On Thu, 3 Apr 2025 12:07:03 GMT, Maurizio Cimadamore <mcimadam...@openjdk.org> wrote:
>> There is a problem here: If we say it is "immutable content" people might >> think that passing mutable data makes it immutable. If we say it is >> "shallowly immutable content" people might think they cannot pass immutable >> data. >> >> I am not so sure that the term "effectively immutable" is widely understood. >> >> Another alternative is to rephrase entirely and say something like >> >> "A stable value is a holder of content that can be lazily computed at most >> once" > >> "A stable value is a holder of content that can be lazily computed at most >> once" > > I'd replace `computed` with `set` (as that's the term we use in the API). `A stable value is a holder of content that can be set at most once` ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/23972#discussion_r2028597302
