On Tue, 19 Mar 2024 00:40:02 GMT, Y. Srinivas Ramakrishna
wrote:
>> Brent Christian has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> further tweaks to reachability
>
> src/java.base/share/classes/java/lang/ref/package-info.java line
On Tue, 19 Mar 2024 22:26:22 GMT, Stuart Marks 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
On Tue, 19 Mar 2024 22:19:50 GMT, David Holmes wrote:
>> In fact, it appears as if the problem is with the use of "any", which is
>> universal in strength, whereas the intention here is existential in strength
>> (as suggested by. my wording). Indeed, you might achieve the same effect by
>>
On Tue, 19 Mar 2024 16:38:49 GMT, Y. Srinivas Ramakrishna
wrote:
>> Sorry, my use of words was sloppy here. I think I did mean loose or somewhat
>> informal and therefore slippery.
>>
>> What I was saying is that using terms such as "any continuing computation"
>> doesn't make sense because
On Tue, 19 Mar 2024 16:20:55 GMT, Y. Srinivas Ramakrishna
wrote:
>> https://docs.oracle.com/javase/specs/jls/se21/html/jls-12.html#jls-12.6.1
>>
>>> A reachable object is any object that can be accessed in any potential
>>> continuing computation from any live thread.
>>
>> It may be
On Tue, 19 Mar 2024 02:53:37 GMT, David Holmes wrote:
>> src/java.base/share/classes/java/lang/ref/package-info.java line 137:
>>
>>> 135: *
>>> 136: * A reachable object is any object that can be accessed in
>>> any potential
>>> 137: * continuing computation from any live thread (as
On Tue, 19 Mar 2024 00:40:02 GMT, Y. Srinivas Ramakrishna
wrote:
>> Brent Christian has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> further tweaks to reachability
>
> src/java.base/share/classes/java/lang/ref/package-info.java line
On Thu, 14 Mar 2024 23:23:07 GMT, Brent Christian wrote:
>> Classes in the `java.lang.ref` package would benefit from an update to bring
>> the spec in line with how the VM already behaves. The changes would focus on
>> _happens-before_ edges at some key points during reference processing.
>>
On Sat, 16 Mar 2024 04:20:44 GMT, Stuart Marks wrote:
>> Brent Christian has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> further tweaks to reachability
>
> src/java.base/share/classes/java/lang/ref/Reference.java line 402:
>
>> 400:
On Sat, 16 Mar 2024 04:21:55 GMT, Stuart Marks wrote:
>> Brent Christian has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> further tweaks to reachability
>
> src/java.base/share/classes/java/lang/ref/package-info.java line 127:
>
>> 125:
On Wed, 31 Jan 2024 01:13:18 GMT, Brent Christian wrote:
>> src/java.base/share/classes/java/lang/ref/package-info.java line 109:
>>
>>> 107: *
>>> 108: * The clearing of a reference by the garbage collector
>>> happens-before
>>> 109: * the garbage collector enqueues the reference.
>>
>>
On Thu, 14 Mar 2024 23:23:07 GMT, Brent Christian wrote:
>> Classes in the `java.lang.ref` package would benefit from an update to bring
>> the spec in line with how the VM already behaves. The changes would focus on
>> _happens-before_ edges at some key points during reference processing.
>>
> Classes in the `java.lang.ref` package would benefit from an update to bring
> the spec in line with how the VM already behaves. The changes would focus on
> _happens-before_ edges at some key points during reference processing.
>
> A couple key things we want to be able to say are:
> -
13 matches
Mail list logo
