@dibblego What’s the problem with not having type erasure?
Erasure is one of the few things that Java got right. C# fell into the trap afterward.
-
-
-
@davetchepak constrains the type system for zero benefit. - Show replies
New conversation -
-
-
-
@josefusbarnabas nasty stuff.
End of conversation
New conversation -
-
-
@dibblego but even with erasure, a lot of java code in the wild is running on reflection-based libs. Don't know if same can be said of C# -
@t4ffer Like@copumpkin said, it would be good if we could remove even more of the nasties!
End of conversation
New conversation -
-
-
@dibblego From a runtime performance POV, it's terrible. But I think it is possible to keep additional type information for the runtime ... -
@oxnrtr That it is possible does have an effect on utility. - Show replies
New conversation -
-
-
@dibblego ...JIT compiler without exposing it to the user of the language. Looking into that right now with runtime specialization in Avian.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@dibblego@svenefftinge so your take on future possible reification in Java is not a good one, then? ;-) -
@lagergren@svenefftinge I am resigned to the super-exponential magnitude of silliness of the future for Java between now and my death.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.