Java's Value Objects Reach OpenJDK Master as JEP 401 Preview

OpenJDK has merged the first preview implementation of JEP 401, which introduces value objects to the Java language. These are class instances that lack identity — no meaningful reference equality, no synchronization lock, no fixed heap location — which frees the JVM to inline them, flatten them into arrays and other objects, and skip heap allocation entirely. This is a foundational piece of Project Valhalla, developed in the valhalla/lworld repository and periodically synced with jdk/master. Because value objects require guaranteed field initialization, the same change set also lands JEP 539, which adds strict field initialization to the JVM; the two features are intertwined and could not be reviewed or shipped separately.

The scale of the work is notable. Rather than review one enormous pull request, the OpenJDK team split it into three area-specific sub-reviews covering the language compiler, the JVM, and the standard library, each carrying the full code set for context while the master PR served only as the integration and sign-off vehicle. The contributor list runs to dozens of engineers, reflecting how deeply value objects touch the runtime, the compiler, and core libraries.

For Java developers, the practical payoff is the ability to write abstractions with the semantics of objects but the performance profile of primitives, reducing pointer chasing and allocation pressure. As a preview feature it remains opt-in and subject to change, but its arrival in master marks a significant milestone for a Valhalla effort that has been in development for years.