While you can create an array reference with a generic type (E[] elements), creating an array object with a generic type (elements = new E[10]) is prohibited. This is due to fundamental differences in how generics and arrays handle type enforcement.
Unlike generics, arrays are covariant. This means that an array of a supertype (e.g., Object[]) can be assigned to an array of a subtype (e.g., String[]). This is not the case with generics, which enforce invariance (e.g., List
Generics enforce stronger type checks at compile time, preventing runtime exceptions and preserving type safety. Arrays, however, carry runtime type information, leading to potential ArrayStoreExceptions if an element of an incompatible type is inserted.
Creating an array with a generic component type (e.g., T[]) is unsafe because the type is not known at runtime. This can lead to type casting errors or ArrayStoreExceptions, as the created array may actually be an Object[] in disguise.
You may wonder why elements = (E[]) new Object[10] appears to work. This is due to unchecked type casting, which suppresses compile-time warnings but still carries the risk of runtime exceptions. In this case, the cast may succeed if the array elements are compatible with the generic type, but it may not always work.
To create an array of a generic type without relying on unchecked casting, use the Array#newInstance() method:
public <E> E[] getArray(Class<E> clazz, int size) { @SuppressWarnings("unchecked") E[] arr = (E[]) Array.newInstance(clazz, size); return arr; }
Creating an array of wildcard parameterized types (e.g., List>[]) is permitted because wildcards are reifiable types that retain their parameterization at runtime. For example, List>[] is equivalent to List[].
The above is the detailed content of Why Can't You Directly Create Generic Arrays in Java?. For more information, please follow other related articles on the PHP Chinese website!