Immutables VS valhalla-docs

This is every Lombok lover's favorite strawman argument I've run into.

I've been coding in Java professionally for ~20 years. I can count with zero hands the number of times I've been burned by a getter or setter getting changed into something surprising.

If you really need auto-generated getters/setters/builders - Immutables [1] is a library that does it using bog standard annotation processing rules that don't require hacking your build process.

[1] https://github.com/immutables/immutables

https://github.com/immutables/immutables/issues/1358 https://bugs.openjdk.java.net/browse/JDK-8281238

That's good, but I prefer this : https://github.com/immutables/immutables It has all sorts of neat stuff like lazy, defered, cached, defaults etc. Just needs updating to use records.

Not bad :) I like using Immutables (which is backed by the style of implementation referenced in the link in https://github.com/immutables/immutables/issues/450)

Annotation processors? Like Immutables? Those already exists, but the major difference is that an annotation processor cannot change the processed class, but has to create another one.

While you’re looking into this I would highly recommend checking out immutables. https://github.com/immutables/immutables It is pretty popular in the industry and very nice!

What isn't clear for me from https://github.com/openjdk/valhalla-docs/blob/main/site/design-notes/state-of-valhalla/02-object-model.md is whether or not value types will indeed be headerless.

Regarding type erasure, see https://github.com/openjdk/valhalla-docs/blob/main/site/design-notes/in-defense-of-erasure.md for a justification. Note in particular that not doing erasure would have forced languages like Scala to follow Java's semantics. In cases where erasure is actually a problem, you can work around it with classes like https://fasterxml.github.io/jackson-core/javadoc/2.2.0/com/fasterxml/jackson/core/type/TypeReference.html.

Here's a (relatively recent) post on type erasure from the lead of the value types project at Oracle https://github.com/openjdk/valhalla-docs/blob/main/site/design-notes/in-defense-of-erasure.md

If you want to read something a little more formal and fleshed out, try scanning through this document, and then come back again and tell me that Brian doesn't understand your suggestion.

Source

I haven't been following it incredibly closely, but I have checked in from time to time. It's a hard problem, but there's a lot of real progress (https://github.com/openjdk/valhalla-docs/blob/main/site/desi...).

I'd wager that it will ship by the next LTS, in 2024.

Quotes from here