Generics are a facility of generic programming that were added to the Java programming language in 2004 within version J2SE 5.0. They were designed to extend Java's type system to allow "a type or method to operate on objects of various types while providing compile-time type safety".[1] The aspect compile-time type safety required that parametrically polymorphicfunctions are not implemented in the Java virtual machine, since type safety is impossible in this case.[2]
The Java collections framework supports generics to specify the type of objects stored in a collection instance.
In 1998, Gilad Bracha, Martin Odersky, David Stoutamire and Philip Wadler created Generic Java, an extension to the Java language to support generic types.[3] Generic Java was incorporated in Java with the addition of wildcards.
According to Java Language Specification:[4]
The following block of Java code illustrates a problem that exists when not using generics. First, it declares an of type . Then, it adds a String to the ArrayList. Finally, it attempts to retrieve the added String and cast it to an Integer—an error in logic, as it is not generally possible to cast an arbitrary string to an integer.
Although the code is compiled without error, it throws a runtime exception (java.lang.ClassCastException) when executing the third line of code. This type of logic error can be detected during compile time by using generics and is the primary motivation for using them. It defines one or more type variables that act as parameters.
The above code fragment can be rewritten using generics as follows:
The type parameter String within the angle brackets declares the ArrayList to be constituted of String (a descendant of the ArrayList's generic Object constituents). With generics, it is no longer necessary to cast the third line to any particular type, because the result of v.get(0) is defined as String by the code generated by the compiler.
The logical flaw in the third line of this fragment will be detected as a compile-time error (with J2SE 5.0 or later) because the compiler will detect that v.get(0) returns String instead of Integer. For a more elaborate example, see reference.[5]
Here is a small excerpt from the definition of the interfaces and in package :
interface Iterator
Here is an example of a generic Java class, which can be used to represent individual entries (key to value mappings) in a map:
This generic class could be used in the following ways, for example:
final Entry
It outputs:
grade: (Mike, A) mark: (Mike, 100) 13 is prime.
Here is an example of a generic method using the generic class above:
Note: If we remove the first <Type> in the above method, we will get compilation error (cannot find symbol "Type"), since it represents the declaration of the symbol.
In many cases, the user of the method need not indicate the type parameters, as they can be inferred:
The parameters can be explicitly added if needed:
The use of primitive types is not allowed, and boxed versions must be used instead:
There is also the possibility to create generic methods based on given parameters.
In such cases you can't use primitive types either, e.g.:
Thanks to type inference, Java SE 7 and above allow the programmer to substitute an empty pair of angle brackets (<>, called the diamond operator) for a pair of angle brackets containing the one or more type parameters that a sufficiently close context implies.[6] Thus, the above code example using Entry can be rewritten as:
final Entry
See main article: Wildcard (Java). A type argument for a parameterized type is not limited to a concrete class or interface. Java allows the use of "type wildcards" to serve as type arguments for parameterized types. Wildcards are type arguments in the form "<?>"; optionally with an upper or lower bound. Given that the exact type represented by a wildcard is unknown, restrictions are placed on the type of methods that may be called on an object that uses parameterized types.
Here is an example where the element type of a Collection<E> is parameterized by a wildcard:
Since we don't know what the element type of c stands for, we cannot add objects to it. The add method takes arguments of type E, the element type of the Collection<E> generic interface. When the actual type argument is ?, it stands for some unknown type. Any method argument value we pass to the add method would have to be a subtype of this unknown type. Since we don't know what type that is, we cannot pass anything in. The sole exception is null; which is a member of every type.[7]
To specify the upper bound of a type wildcard, the keyword is used to indicate that the type argument is a subtype of the bounding class. So means that the given list contains objects of some unknown type which extends the Number class. For example, the list could be List<Float> or List<Number>. Reading an element from the list will return a Number. Adding null elements is, again, also allowed.[8]
The use of wildcards above adds flexibility since there is not any inheritance relationship between any two parameterized types with concrete type as type argument. Neither List<Number> nor List<Integer> is a subtype of the other; even though Integer is a subtype of Number. So, any method that takes List<Number> as a parameter does not accept an argument of List<Integer>. If it did, it would be possible to insert a Number that is not an Integer into it; which violates type safety. Here is an example that demonstrates how type safety would be violated if List<Integer> were a subtype of List<Number>:
The solution with wildcards works because it disallows operations that would violate type safety:
To specify the lower bounding class of a type wildcard, the super keyword is used. This keyword indicates that the type argument is a supertype of the bounding class. So, could represent List<Number> or List<Object>. Reading from a list defined as returns elements of type Object. Adding to such a list requires either elements of type Number, any subtype of Number or null (which is a member of every type).
The mnemonic PECS (Producer Extends, Consumer Super) from the book Effective Java by Joshua Bloch gives an easy way to remember when to use wildcards (corresponding to covariance and contravariance) in Java.
Although exceptions themselves cannot be generic, generic parameters can appear in a throws clause:
Generics are checked at compile-time for type-correctness. The generic type information is then removed in a process called type erasure. For example, List<Integer> will be converted to the non-generic type List, which ordinarily contains arbitrary objects. The compile-time check guarantees that the resulting code uses the correct type.
Because of type erasure, type parameters cannot be determined at run-time. For example, when an ArrayList is examined at runtime, there is no general way to determine whether, before type erasure, it was an ArrayList<Integer> or an ArrayList<Float>. Many people are dissatisfied with this restriction.[9] There are partial approaches. For example, individual elements may be examined to determine the type they belong to; for example, if an ArrayList contains an Integer, that ArrayList may have been parameterized with Integer (however, it may have been parameterized with any parent of Integer, such as Number or Object).
Demonstrating this point, the following code outputs "Equal":
Another effect of type erasure is that a generic class cannot extend the Throwable class in any way, directly or indirectly:[10]
Java generics differ from C++ templates. Java generics generate only one compiled version of a generic class or function regardless of the number of parameterizing types used. Furthermore, the Java run-time environment does not need to know which parameterized type is used because the type information is validated at compile-time and is not included in the compiled code. Consequently, instantiating a Java class of a parameterized type is impossible because instantiation requires a call to a constructor, which is unavailable if the type is unknown.
For example, the following code cannot be compiled:
Because there is only one copy per generic class at runtime, static variables are shared among all the instances of the class, regardless of their type parameter. Consequently, the type parameter cannot be used in the declaration of static variables or in static methods.
Type erasure was implemented in Java to maintain backward compatibility with programs written prior to Java SE5.
There are several important differences between arrays (both primitive arrays and arrays), and generics in Java. Two of the major differences, namely, differences in terms of variance and reification.
See main article: article and Covariance and contravariance (computer science). Generics are invariant, whereas arrays are covariant. This is a benefit of using generic when compared to non-generic objects such as arrays. Specifically, generics can help prevent run time exceptions by throwing a compile-time exception to force the developer to fix the code.
For example, if a developer declares an object and instantiates the object as a new object, no compile-time exception is thrown (since arrays are covariant). This may give the false impression that the code is correctly written. However, if the developer attempts to add a to this object, the program will throw an . This run-time exception can be completely avoided if the developer uses generics.
If the developer declares a object an creates a new instance of this object with return type, the Java compiler will (correctly) throw a compile-time exception to indicate the presence of incompatible types (since generics are invariant). Hence, this avoids potential run-time exceptions. This problem can be fixed by creating an instance of using object instead. For code using Java SE7 or later versions, the can be instantiated with an object using the diamond operator
See main article: article and Reification (computer science). Arrays are reified, meaning that an array object enforces its type information at run-time, whereas generics in Java are not reified.
More formally speaking, objects with generic type in Java are non-reifiable types. A non-reifiable type is type whose representation at run-time has less information than its representation at compile-time.
Objects with generic type in Java are non-reifiable due to type erasure. Java only enforces type information at compile-time. After the type information is verified at compile-time, the type information is discarded, and at run-time, the type information will not be available.
Examples of non-reifiable types include and, where is a generic formal parameter.
Project Valhalla is an experimental project to incubate improved Java generics and language features, for future versions potentially from Java 10 onwards. Potential enhancements include:[11]