[concurrency-interest] Future.isCompletedNormally Future.isCompletedAbnormally
martinrb at google.com
Thu Mar 5 10:27:05 EST 2015
Even isDone is not (yet) mentioned in
Memory Consistency Properties
All of the is* methods would (obviously) have the same happens-before
On Wed, Mar 4, 2015 at 10:58 PM, thurstonn <thurston at nomagicsoftware.com>
> What would be the memory consistency effects of
> isCompletedNormally() ==> true be?
> I assume the "asynchronous computation" would happen-before in that case.
> Also, just for discussion, what if you have some :
> DefaultFuture<T>(default:T, () -> T) implements Future<T>
> what would the semantics of isCompletedAbnormally() be in such a case?
> Might burden the implementation unnecessarily in such a case to strictly
> implement it.
> I'm not sure how FJP uses FJT's methods, but it doesn't necessarily follow
> that those methods should be promoted to the base interface.
> View this message in context:
> Sent from the JSR166 Concurrency mailing list archive at Nabble.com.
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Concurrency-interest