[concurrency-interest] ManagedBlocker.block() documentation

Tim Peierls tim at peierls.net
Wed Oct 30 09:58:45 EDT 2019


"return" -> "returns" ?

On Wed, Oct 30, 2019, 9:50 AM Doug Lea via Concurrency-interest <
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
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20191030/9e5c7b49/attachment.html>


More information about the Concurrency-interest mailing list