Heap pollution

In the

runtime heap pollution will often cause a ClassCast Exception.^[2]

Heap pollution in Java can occur when type arguments and variables are not

implemented by the same class or interface at run time. All invocations of a given generic type declaration share a single run-time implementation. This results in the possibility of heap pollution.^[2]

Under certain conditions, a variable of a parameterized type may refer to an object that is not of that parameterized type. The variable will always refer to an object that is an instance of a class that implements the parameterized type.

Heap Pollution in a non-varargs context

public class HeapPollutionDemo
{
    public static void main(String[] args)
    {
        Set s = new TreeSet<Integer>();
        Set<String> ss = s;              // unchecked warning
        s.add(new Integer(42));          // another unchecked warning
        Iterator<String> iter = ss.iterator();

        while (iter.hasNext())
        {
            String str = iter.next();    // ClassCastException thrown
            System.out.println(str);
        }
    }
}

References

^ ^a ^b "The Java SE Tutorials". Oracle. Retrieved 16 July 2014.
^ ^a ^b Langer, Angelika. "Java Generics FAQs: Heap pollution". angelikalanger.com/. Retrieved 15 July 2014.

This programming-language-related article is a stub. You can help Wikipedia by expanding it.

[Java-1] "The Java SE Tutorials". Oracle. Retrieved 16 July 2014.

[Langer-2] Langer, Angelika. "Java Generics FAQs: Heap pollution". angelikalanger.com/. Retrieved 15 July 2014.

[2]

Further reading

References