The OpenJDK Amber project has published a new design note proposing “carrier classes” and “carrier interfaces” to extend record-style data modeling to more Java types. The proposal preserves concise s

InfoQ is a leading online platform for software developers, architects, and technical leaders, providing news, articles, presentations, and interviews on a wide range of topics, including agile practices, DevOps, microservices, and emerging technologies. With a focus on quality content and expert insights, InfoQ helps professionals stay informed about the latest trends, best practices, and industry developments. Developers can learn from real-world experiences, gain  knowledge, and connect with peers in the global software community through InfoQ's diverse and engaging content.

InfoQ

OpenJDK's Project Amber has proposed "carrier classes" and "carrier interfaces" to extend record-like capabilities to more flexible Java class designs. While records (introduced in Java 16) provide concise immutable data modeling with auto-generated methods and pattern matching support, they have strict constraints that limit their use in real-world scenarios requiring derived values, caching, mutability, or inheritance. Carrier classes would allow developers to define a state description similar to records while maintaining the flexibility of traditional classes, enabling patterns like cached computed values and alternative internal representations. The proposal also introduces carrier interfaces for pattern matching across implementations. This exploratory design note aims to reduce boilerplate and support Java's shift toward data-oriented programming, though no concrete syntax or release timeline has been announced.

Java Explores Carrier Classes to Extend Data-Oriented Programming Beyond Records