I can see that for "obsolete" libraries, but I have trouble seeing that happening for reified generics. Don't reified generics start at compile time? i.e. is the type erasure is done by javac? If so, I don't see how a modular runtime could help.
On Jan 12, 8:27 am, Jess Holle <je...@ptc.com> wrote: > Weiqi Gao wrote: > > Now that the Java 7 feature set has been redefined and (provisionally > > and non-bindingly) finalized (again), and my (and I think a lot of > > others') favorite features are not in it, I think it's time to start > > compile a wish list for Java 8 and Java 9. > > > Here's mine: > > > Java 8: > > > Reified generics > > Removal of dead features (java.awt.Button, etc.) > > A large benefit of modularization ala Jigsaw is that you don't have to > remove stuff like this (which you really can't without breaking a lot of > applications). Instead it goes into an obsolete/deprecated module which > you just never load if you don't use it. > > Ideally Javadoc gets updated to hide such cruft by default as well. > > Then you get the best of both worlds -- nothing breaks, but you don't > have to pay for cruft in any real sense. > > -- > Jess Holle --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
