3 ms·
To what degree do these features translate to JVM changes, vs just Java language changes (I know the two are fairly tightly coupled)? Eg will this mean new byte
by brundolf 3y ago
To what degree do these features translate to JVM changes, vs just Java language changes (I know the two are fairly tightly coupled)? Eg will this mean new bytecode/optimizations that could be used to optimize other JVM languages which already have similar features?
- quantumwoke 3y agoYes, you can read more about the JVM changes in this blog post: https://openjdk.org/projects/valhalla/design-notes/state-of-valhalla/03-vm-model https://openjdk.org/projects/valhalla/design-notes/state-of-...
- brundolf 3y agoNice. So for example, it looks like Kotlin already has a nearly identical feature at the language level, which will be optimizable when Valhalla ships: https://github.com/Kotlin/KEEP/blob/master/notes/value-classes.md https://github.com/Kotlin/KEEP/blob/master/notes/value-class... > In the future, in a Valhalla-capable JVM, JVM primitive classes will enable efficient representation of Kotlin value classes with an arbitrary number of underlying fields on JVM.
- pjmlp 3y agoExcept it will mean that the semantics will be observable between JVM, ART, and all remaining Kotlin targets.