On Jan 27, 7:18 pm, Reinier Zwitserloot <reini...@gmail.com> wrote: > The generics design team was very much aware of the usefulness of > reification, but did not see a way to add it without seriously > breaking backwards compatibility. Java 1.5 already came with a giant > bag of changes, and it was at some point dropped in favour of type > erasure. I haven't looked too closely at it, but I know there's a > supposedly quite complete proposal out there to add it at some point.
Generics with reification doesn't break backwards compatibility, it breaks /migration/ compatibility. That means, essentially, that it would have required leaving the existing collections classes alone - without generics - and creating a new set of collection classes to take advantage of generics. I am aware of no proposals to add reification in a migration-compatible way. Dropping the requirement for migration compatibility was never on the table for jsr14, so it isn't correct to say that it was "dropped" due to resource constraints. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
