On Fri, 24 Apr 2026 09:02:04 GMT, Per Minborg <[email protected]> wrote:
>> Implement JEP 531: Lazy Constants (Third Preview) >> >> This PR replaces _draft_ https://github.com/openjdk/jdk/pull/29507 >> >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Per Minborg has updated the pull request incrementally with one additional > commit since the last revision: > > Change the way throwing toString is handled src/java.base/share/classes/java/lang/LazyConstant.java line 51: > 49: * {@linkplain LazyConstant#of(Supplier) LazyConstant.of({@code > <computing function>})}. > 50: * <p> > 51: * When created, the lazy constant is <em>not initialized</em>, meaning > it has no content. I wonder if it might be better to use `uninitialized` as a word, and then re-use that throughout to describe `not initialized`. src/java.base/share/classes/java/lang/LazyConstant.java line 279: > 277: > 278: /** > 279: * {@return a new lazy constant whose content is to be computed > later via the Switching to `uninitialized` to describe the initial state, makes it possible to then re-use that verbiage to explain it in the following way: Suggestion: * {@return a new, uninitialized, lazy constant whose content is to be computed later via the ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/30194#discussion_r3146195173 PR Review Comment: https://git.openjdk.org/jdk/pull/30194#discussion_r3146207934
