Here's the story of what I found looking for constructs that the compiler and/or specification claim are safe, do not generate warnings, but cause heap pollution, leading to a ClassCastException where there is no explicit cast.
Here's the story of what I found looking for constructs that the compiler and/or specification claim are safe, do not generate warnings, but cause heap pollution, leading to a ClassCastException where there is no explicit cast.