RFR: 8314480: Memory ordering spec updates in java.lang.ref [v13]

[Y. Srinivas Ramakrishna]

On Tue, 19 Mar 2024 22:26:22 GMT, Stuart Marks <smarks at openjdk.org> wrote:

>> I think you are overthinking this somewhat Ramki. I don't see a practical (non discrete-math) distinction between "some" and "any", so would not object to that single word change if it helps. But "potential" should remain as it covers branching in the program whereby if we proceed down one branch an object remains reachable, whereas if we precede down another then it may not.
>
> I don't think changing "any" to "some" is helpful. I think "any" is ambiguous regarding meaning universal or existential strength. The sense used here is, considering the possible future execution paths of a thread, if any of them accesses the object, that object is reachable. In other words, it means "any one" and not "all".

OK, no worries; will let you decide what makes sense. Thanks!

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

PR Review Comment: https://git.openjdk.org/jdk/pull/16644#discussion_r1531559810