jdk.util.concurrent.CompletableFuture

Liking cljdoc? Tell your friends :D

Clojure only.

A Future that may be explicitly completed (setting its value and status), and may be used as a CompletionStage, supporting dependent functions and actions that trigger upon its completion.

When two or more threads attempt to complete, completeExceptionally, or cancel a CompletableFuture, only one of them succeeds.

In addition to these and related methods for directly manipulating status and results, CompletableFuture implements interface CompletionStage with the following policies:

Actions supplied for dependent completions of non-async methods may be performed by the thread that completes the current CompletableFuture, or by any other caller of a completion method.

All async methods without an explicit Executor argument are performed using the ForkJoinPool.commonPool() (unless it does not support a parallelism level of at least two, in which case, a new Thread is created to run each task). To simplify monitoring, debugging, and tracking, all generated asynchronous tasks are instances of the marker interface CompletableFuture.AsynchronousCompletionTask.

All CompletionStage methods are implemented independently of other public methods, so the behavior of one method is not impacted by overrides of others in subclasses.

CompletableFuture also implements Future with the following policies:

Since (unlike FutureTask) this class has no direct control over the computation that causes it to be completed, cancellation is treated as just another form of exceptional completion. Method cancel has the same effect as completeExceptionally(new CancellationException()). Method isCompletedExceptionally() can be used to determine if a CompletableFuture completed in any exceptional fashion.

In case of exceptional completion with a CompletionException, methods get() and get(long, TimeUnit) throw an ExecutionException with the same cause as held in the corresponding CompletionException. To simplify usage in most contexts, this class also defines methods join() and getNow(T) that instead throw the CompletionException directly in these cases.

A Future that may be explicitly completed (setting its
value and status), and may be used as a CompletionStage,
supporting dependent functions and actions that trigger upon its
completion.

When two or more threads attempt to
complete,
completeExceptionally, or
cancel
a CompletableFuture, only one of them succeeds.

In addition to these and related methods for directly
manipulating status and results, CompletableFuture implements
interface CompletionStage with the following policies:

Actions supplied for dependent completions of
non-async methods may be performed by the thread that
completes the current CompletableFuture, or by any other caller of
a completion method.

All async methods without an explicit Executor
argument are performed using the ForkJoinPool.commonPool()
(unless it does not support a parallelism level of at least two, in
which case, a new Thread is created to run each task).  To simplify
monitoring, debugging, and tracking, all generated asynchronous
tasks are instances of the marker interface CompletableFuture.AsynchronousCompletionTask.

All CompletionStage methods are implemented independently of
other public methods, so the behavior of one method is not impacted
by overrides of others in subclasses.

CompletableFuture also implements Future with the following
policies:

Since (unlike FutureTask) this class has no direct
control over the computation that causes it to be completed,
cancellation is treated as just another form of exceptional
completion.  Method cancel has the same effect as
completeExceptionally(new CancellationException()). Method
isCompletedExceptionally() can be used to determine if a
CompletableFuture completed in any exceptional fashion.

In case of exceptional completion with a CompletionException,
methods get() and get(long, TimeUnit) throw an
ExecutionException with the same cause as held in the
corresponding CompletionException.  To simplify usage in most
contexts, this class also defines methods join() and
getNow(T) that instead throw the CompletionException directly
in these cases.

jdk.util.concurrent.CompletableFuture

*all-ofclj

*any-ofclj

*completed-futureclj

*run-asyncclj

*supply-asyncclj

->completable-futureclj

accept-eitherclj

accept-either-asyncclj

apply-to-eitherclj

apply-to-either-asyncclj

cancelclj

cancelled?clj

completeclj

complete-exceptionallyclj

completed-exceptionally?clj

done?clj

exceptionallyclj

getclj

get-nowclj

get-number-of-dependentsclj

handleclj

handle-asyncclj

joinclj

obtrude-exceptionclj

obtrude-valueclj

run-after-bothclj

run-after-both-asyncclj

run-after-eitherclj

run-after-either-asyncclj

then-acceptclj

then-accept-asyncclj

then-accept-bothclj

then-accept-both-asyncclj

then-applyclj

then-apply-asyncclj

then-combineclj

then-combine-asyncclj

then-composeclj

then-compose-asyncclj

then-runclj

then-run-asyncclj

to-completable-futureclj

to-stringclj

when-completeclj

when-complete-asyncclj

*all-of^clj

*any-of^clj

*completed-future^clj

*run-async^clj

*supply-async^clj

->completable-future^clj

accept-either^clj

accept-either-async^clj

apply-to-either^clj

apply-to-either-async^clj

cancel^clj

cancelled?^clj

complete^clj

complete-exceptionally^clj

completed-exceptionally?^clj

done?^clj

exceptionally^clj

get^clj

get-now^clj

get-number-of-dependents^clj

handle^clj

handle-async^clj

join^clj

obtrude-exception^clj

obtrude-value^clj

run-after-both^clj

run-after-both-async^clj

run-after-either^clj

run-after-either-async^clj

then-accept^clj

then-accept-async^clj

then-accept-both^clj

then-accept-both-async^clj

then-apply^clj

then-apply-async^clj

then-combine^clj

then-combine-async^clj

then-compose^clj

then-compose-async^clj

then-run^clj

then-run-async^clj

to-completable-future^clj

to-string^clj

when-complete^clj

when-complete-async^clj