When will Java have Value Classes/Value Types?

This market predicts when the mainstream Java programming language will support Value Classes (also known as Value Types). A Value Type qualifies only if it meets the following criteria and is available as a language feature in a production-quality, mainstream JDK (Java Development Kit): Definition of Value Types: Value Types are a new kind of type in Java, designed to be lightweight, immutable, and without identity. They have the following characteristics: Immutability: Instances of Value Types are immutable, meaning their state cannot be changed after creation. Equality: Value Types support == for value-based equality, comparing their constituent values (at least as a default behavior). Instance Methods: Value Types can contain code, including instance methods, allowing them to have behavior in addition to state. No Identity: Value Types do not have object identity, meaning they cannot be compared using identity comparison (e.g., System.identityHashCode). Direct Containment in Arrays: Value Types can be stored directly in arrays without boxing, meaning they are stored as their raw values rather than as references. Exit from Preview: The feature must exit the preview release phase and be officially included in a stable, production-quality release of the JDK. This means the feature must be finalized and available in a major JDK release that is intended for widespread use and adoption. Mainstream JDKs: The feature must be included in a mainstream JDK distribution such as OpenJDK, Oracle JDK, or other widely recognized JDK distributions that are used in production environments. This market will resolve based on the earliest official release date of a production-quality JDK that includes Value Types as described above. The market will be updated with new options until the feature becomes available. Each option represents a time frame by which the feature is predicted to be available. The option resolves YES if the feature is available ON or BEFORE the date, otherwise it resolves NO. If the planned feature is officially abandoned (through the Java Community Process), and there is no proposed replacement feature that would satisfy the criteria, then the option "Never" will resolve YES and all other options resolve NO. Resolution date will be extended as necessary.