3 ms·
The best thing about this is VM support for records. This means that all the other JVM languages that implement similar features can potentially leverage the u
by davewritescode 7y ago
The best thing about this is VM support for records. This means that all the other JVM languages that implement similar features can potentially leverage the underlying support for records to make better implementations themselves.
I for example, don’t immediately see any reason kotlin can’t use this to make a more efficient implementation of data classes.
- kllrnohj 7y agoWhat VM support? Records are a Java compiler feature. It just auto-generates all the boilerplate at compile time, there doesn't seem to be any bytecode or VM support for this feature? It seems functionally identical at the VM/bytecode level to what Kotlin's data classes already do.
- davewritescode 7y agoMy mistake, I thought this was more akin to value types proposed in this JEP https://openjdk.java.net/jeps/169 https://openjdk.java.net/jeps/169 This is disappointing.
- pron 7y agoRecords are meant to play nicely with inline types, i.e. when inline types land, you'll be able to declare inline records.