[concurrency-interest] Future.isCompletedNormally Future.isCompletedAbnormally

Martin Buchholz martinrb at google.com
Thu Mar 5 10:27:05 EST 2015


Even isDone is not (yet) mentioned in
Memory Consistency Properties

in
http://docs.oracle.com/javase/8/docs/api/java/util/concurrent/package-summary.html

All of the is* methods would (obviously) have the same happens-before
semantics.

On Wed, Mar 4, 2015 at 10:58 PM, thurstonn <thurston at nomagicsoftware.com>
wrote:

> 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:
> http://jsr166-concurrency.10961.n7.nabble.com/Future-isCompletedNormally-Future-isCompletedAbnormally-tp12386p12397.html
> Sent from the JSR166 Concurrency mailing list archive at Nabble.com.
> _______________________________________________
> 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/20150305/0d586116/attachment.html>


More information about the Concurrency-interest mailing list