[External] : Re: A new build and a new structured concurrency API
    Ron Pressler 
    ron.pressler at oracle.com
       
    Mon Nov 15 23:20:08 UTC 2021
    
    
  
> On 15 Nov 2021, at 22:01, Mike Rettig <mike.rettig at gmail.com> wrote:
> 
> 
> I think the cancellation mechanism needs to be addressed first. The "correct" way to handle thread interrupts is already unclear in many cases. Requiring it to mean "cancel" when used with structured concurrency is going to be difficult for developers.
> 
Cancellation is mentioned in the non-goals section of the JEP precisely because we acknowledge there’s a problem
that will be addressed by *other* work. Interruption is the only cancellation mechanism we currently have in the JDK, 
and it is already supported by most blocking APIs. We believe that we’ll be able to offer an alternative that could be 
compatible with interruption (and, therefore, not require an API change here), but that alternative will be offered 
separately. For the moment, reporting on your experience with this JEP would be helpful.
— Ron
    
    
More information about the loom-dev
mailing list