|
|
|
|
|
by nicolai-parlog
1873 days ago
|
|
1. with possible loss of information
2. as API, but an operator can do more
3. they are surely serializable, but they still need all the ugly reflection hacks that come with that (like bypassing the constructor and allowing the JVM to write to final fields)
4. that part was just presenting a benefit of records (on its own; not over Lombok/Kotlin), but the fact it's under the header "Why Records Are Better*" is confusing |
|