added students solution to review

[JJJazl]

No description provided.

[JJJazl]

Please don't add redundant imports and commented lines to your code

[JJJazl]

Please don’t add redundant empty lines to your code

[JJJazl]

1. Pay attention to constants naming convention
   https://mate-academy.github.io/style-guides/java/java.html#s5.2.4-constant-names
2. Use a full name for variables to make code more clear. For example:

private static final int DEFAULT_CAPACITY = 10;

[JJJazl]

Please don’t add redundant empty lines to your code

[JJJazl]

1. Use informative names for your variables. For example, elementData provides more insight than an array
2. Redundant typecast to generic array. Generic type T will be erased to Object after compilation, so you can directly use a Object[]
   Example below:
   private Object[] elementData;
3. It might be better to have 2 constructors in order to initialize ArrayList with default and specified initial capacity, but maybe it's not a required for this task, so I will specify it to be sure. Anyway, you can see how it would look like below:

public ArrayList() {
        this.elementData = EMPTY_ARRAYDATA;
    }

    public ArrayList(int initialCapacity) {
        if (initialCapacity < 0) {
            throw new IllegalArgumentException("Initial capacity must be great than 0");
        }
        this.elementData = new Object[initialCapacity];
    }

[JJJazl]

1. This method is not a part of public API, so make it private and non-static
2. Use List with generic type T instead of raw type, because we want to be sure we stick to the same type
   P.S. you can use @SuppressWarnings("unchecked") to avoid "Unchecked cast: 'java.lang.Object[]' to 'T[]'" warning
   Example below:

@SuppressWarnings("unchecked")
public T[] listToArray(List<T> list) {
}

[JJJazl]

It can cause a NPE, so return an EMPTY_ARRAYDATA instead

[JJJazl]

You can just check if size == 0. It will be O(1) instead of O(n) time complexity

[JJJazl]

1. It seems like copy of the original ArrayList using the found label. This is generally considered as a bad practice, because it makes code more verbose and harder to read, so I suggest rewrite it simply using for statements.
2. Make your exceptions informative
   https://mate-academy.github.io/jv-program-common-mistakes/java-core/collections/array-list.html#make-your-exceptions-informative

[JJJazl]

Please don’t add redundant empty lines to your code