RFR: 8254275: Development to revise ValueBased.html for consistency with inline class migration

Dan Smith dlsmith at openjdk.java.net
Fri Oct 9 20:38:14 UTC 2020


On Fri, 9 Oct 2020 20:26:31 GMT, Dan Smith <dlsmith at openjdk.org> wrote:

> Polishing the specification of "value-based class" to align with requirements of inline classes, allow classes (like
> Integer) with deprecated constructors, and clarify expectations for clients.

src/java.base/share/classes/java/lang/doc-files/ValueBased.html line 42:

> 40:         objects);</li>
> 41:     <li>extend either <code>Object</code> or a hierarchy of abstract classes that
> 42:         declare no instance fields and have no instance initialization logic</li>

This is new, and is relevant only to suitability for inline class migration. But it's true for all classes that claim
to be value-based, so seems like a reasonable thing to state, and a good way to encourage people who care about this
concept to structure their API in a migration-friendly way.

-------------

PR: https://git.openjdk.java.net/valhalla/pull/222



More information about the valhalla-dev mailing list