News for hackers. Stuff that matters.
Re:Java 10 – Specification for Value Types by jimktrains2 on Monday June 19, 2017 @02:23AM (#14584917)
I meant breaking in that the Java 10 compiler would be targeting a newer version of the JVM and could dispense with having to be backwards compatible, which was one of the reasons I remember reading for generics.

They could have simply left the old library, deprecated it, and added in their genericed one as a a new package. It had to be modified anyway.

Re:Java 10 – Specification for Value Types by evincarofautumn on Monday June 19, 2017 @03:08AM (#14585077)
Right, it breaks forward compatibility: bytecode for a newer VM won’t work on an older VM. IMO backward compatibility is much more important for a programming language, though.
Re:Java 10 – Specification for Value Types by jdmichal on Monday June 19, 2017 @07:25AM (#14586061)
Or they could have done erasure in the runtime when they detected non-generic usage of a generic class. Instead of forcing it on everyone.
Re:Java 10 – Specification for Value Types by moomin on Monday June 19, 2017 @03:19AM (#14585115)
Yup, and Microsoft did exactly that, meaning C# has been able to express List<int> for ten years now.