3 ms·
This should address your example https://openjdk.org/jeps/218 https://openjdk.org/jeps/218
by za3faran 18d ago
This should address your example https://openjdk.org/jeps/218 https://openjdk.org/jeps/218
- PaulHoule 18d agoI am looking forward to it, and many other things planned for Java!
- AgentME 17d agoThat's about letting you do Expression<int>, not about removing type erasure or otherwise allowing overloads based on type parameters.
- gf000 17d agoIt's one end of the same problem. int is not an Object, so just erasing is no longer a valid approach, you need to specialize the class/method itself to use int-specific byte code.
- dwaite 17d agoThat is unfortunately more about adding another edge case for the non-reified Java generics system where it has been forced to partially reify, rather than really addressing the larger complaint.
- za3faran 17d agoIt should address the most common use case for reification. Type erasure has its advantages which we saw in the JVM ecosystem.