Candidate JEP 390 (“Warnings for Value-Based Classes”) was announced this past week by Mark Reinholdon the OpenJDK jdk-dev mailing list. This is a JDK Enhancement Proposal that may be more exciting in what it indicates (progress toward inline classes) than what it actually is (annotation and warnings about “improper attempts to synchronize on instances” of **@ValueBased**-annotated JDK classes that might be come inline classes).

The term " Value-based Classes" was included in the Java SE 8 Javadoc documentation, which identified the following characteristics of “instances of a value-based class” at that time:

  • final and immutable (though may contain references to mutable objects)”
  • Implement “equalshashCode, and toString … solely [computed] from the instance’s state and not from its identity or the state of any other object or variable”
  • Do NOT use “identity-sensitive operations such as reference equality (==) between instances, identity hash code of instances, or synchronization on an instances’s intrinsic lock”
  • “Are considered equal solely based on equals()” rather than “on reference equality (==)”
  • “Instantiated through factory methods which make no committment as to the identity of returned instances” rather than providing accessible constructors
  • “Are freely substitutable when equal”

That Java SE 8 documentation also warned that “a program may produce unpredictable results if it attempts to distinguish two references to equal values of a value-based class, whether directly via reference equality or indirectly via an appeal to synchronization, identity hashing, serialization, or any other identity-sensitive mechanism.” It further emphasizes, “Use of such identity-sensitive operations on instances of value-based classes may have unpredictable effects and should be avoided.” This documentation remains essentially the same today (Java 15). This documentation is linked to from certain identified JDK classes’ Javadoc comments. A good overview on value-based classes is available in Nicolai Parlog’s blog post " Value-Based Classes."

Although some JDK classes have been identified in their Javadoc as value-based classes since Java 8, JEP 390 aims to provide the annotation **@ValueBased** for these types of JDK classes. The annotation is a stronger construct than a comment and is specifically intended to be used in conjunction with “warnings about improper attempts to synchronize on instances of such classes.” The advantage of such an annotation is that developers can be warned about current uses in their code to synchronize on instances of classes that may one day be unsuitable for such synchronization. Because some likely significant time will pass between the availability of this warning and the actual coversion of these @ValueBased-annotated classes to inline classes (the JEP word this as, “several releases before the migration occurs”), developers will have ample opportunity to change the classes upon which they apply synchronization.

The warning about use of JDK classes for synchronization has benefit in its own right. In addition, I think this JEP is an exciting step toward inline types and the JEP is full of details about inline types. Specifically, the first paragraph of the “Motivation” section of JEP 390 states:

#java #openjdk #annotation #inline classes #valuebased

Moving Toward Inline Classes: JEP 390 and the @ValueBased Annotation
1.10 GEEK