[concurrency-interest] We need to add blocking methods to CompletionStage!
szegedia at gmail.com
Mon Sep 26 21:29:11 UTC 2016
Not at all, you could just have a call to cancel() block until the future completes.
> On 25 Sep 2016, at 16:34, Viktor Klang <viktor.klang at gmail.com> wrote:
> If that truely is the case then the only way of implementing a readonly
> Future is by throwing an exception from cancel...
> On Sep 25, 2016 4:20 PM, "Joe Bowbeer" <joe.bowbeer at gmail.com> wrote:
>> This statement regarding what happens after cancel is called is correct:
>> "*After this method returns, subsequent calls to **isDone**() will always
>> return true*. Subsequent calls to isCancelled() will always return true
>> if this method returned true."
>> After cancel returns, the future is completed, hence isDone. If cancel
>> returns true, i.e. it was cancelled, then isCancelled returns true. But,
>> for example if the future is already completed when cancel is called, then
>> cancel will return false and isCancelled will return false.
>> On Sep 25, 2016 6:49 AM, "David Holmes" <davidcholmes at aapt.net.au> wrote:
>>> I think that was meant to read “After this method returns _*true*_,
>>> subsequent calls …”
More information about the core-libs-dev