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/util/Set.java line 748: > 746: * computed via the provided {@code computingFunction} on > demand} > 747: * <p> > 748: * In the following, the term <em>membership status</em> means > whether an element is a Not sure what the adjective "logical" buys. E.g. "whether an element is a member of the returned set" More generally, I'd rewrite like this: `In the following, the term membership status is used to indicate whether an element belongs to the returned set. That is, if the membership status for element E is `true`, then E is a member of the returned set. Conversely, if the membership status for element E is `false`,then E is not a member of the returned set.` src/java.base/share/classes/java/util/Set.java line 793: > 791: * The returned Set is <em>not</em> {@linkplain Serializable}. > 792: * <p> > 793: * Here is an example involving an application that manages various > configurable Here we provide an example when to use this-- but there's no such examples for lazy List/Map. Was this added because the use case for lazy set feels more obscure? ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/30194#discussion_r3146137987 PR Review Comment: https://git.openjdk.org/jdk/pull/30194#discussion_r3146143190
