[concurrency-interest] ManagedBlocker.block() documentation

Doug Lea dl at cs.oswego.edu
Wed Oct 30 10:23:15 EDT 2019


On 10/30/19 9:58 AM, Tim Peierls via Concurrency-interest wrote:
> "return" -> "returns" ?

Right; thanks. Plus we can further simplify as:

     * Neither method is invoked after a prior invocation
     * of {@code isReleasable} or {@code block} returns {@code true}.

> 
> On Wed, Oct 30, 2019, 9:50 AM Doug Lea via Concurrency-interest
> <concurrency-interest at cs.oswego.edu
> <mailto:concurrency-interest at cs.oswego.edu>> wrote:
> 
>     On 10/30/19 3:23 AM, Roman Leventov via Concurrency-interest wrote:
>     > Currently, ManagedBlocker's documentation doesn't clarify whether the
>     > execution framework could call block() more than once or not. The
>     > specification for the return value of block() method:
> 
>     This seems implicit in the interface-level description, but we'll add a
>     clarification:
> 
>          * Method {@code block} is not invoked after a prior invocation of
>          * {@code isReleasable} or {@code block} return {@code true}.
>          *
> 
>     -Doug
> 
>     _______________________________________________
>     Concurrency-interest mailing list
>     Concurrency-interest at cs.oswego.edu
>     <mailto:Concurrency-interest at cs.oswego.edu>
>     http://cs.oswego.edu/mailman/listinfo/concurrency-interest
> 
> 
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest
> 




More information about the Concurrency-interest mailing list