Native methods and virtual threads

[Jorn Vernee]

They are not the same. A system property isn't necessarily part of the 
Java SE specification. The process for the two is very different. The 
commitment to adding a Linker.Option is much larger. It shouldn't be 
something we add or remove willy nilly.

Also, at the risk of stating the obvious: implementing the option is not 
trivial. This is also time and effort invested into something that, at 
the moment, we only just _think_ need. I'd rather focus on other things 
until we have more evidence that this is the right thing to do.

Jorn

On 14/07/2023 20:08, Brian S O'Neill wrote:
> A hint is a very weak change to a specification. It's in the same 
> league as a magic system property like 
> "jdk.virtualThreadScheduler.maxPoolSize"
>
> I'm interested in any other details you have regarding the decision to 
> incorporate the Blocker class. Thanks!
>
> On 2023-07-14 10:59 AM, Ron Pressler wrote:
>> What we were discussing here wasn't an optimisation but your 
>> suggestion to change the specification. As to Blocker, if you’re 
>> interested in the details of the technical considerations and tests 
>> involved, I’ll try to find the time to talk to the relevant people 
>> and get back to you.
>>