← 返回首页
Future (Java SE 26 & JDK 26)
JavaScript is disabled on your browser.
Contents  
  1. Description
  2. Nested Class Summary
  3. Method Summary
  4. Method Details
    1. cancel(boolean)
    2. isCancelled()
    3. isDone()
    4. get()
    5. get(long, TimeUnit)
    6. resultNow()
    7. exceptionNow()
    8. state()
Hide sidebar  Show sidebar

Interface Future<V>

Type Parameters: V - The result type returned by this Future's get method All Known Subinterfaces: RunnableFuture<V>, RunnableScheduledFuture<V>, ScheduledFuture<V> All Known Implementing Classes: CompletableFuture, CountedCompleter, ForkJoinTask, FutureTask, RecursiveAction, RecursiveTask, SwingWorker
public interface Future<V>
A Future represents the result of an asynchronous computation. Methods are provided to check if the computation is complete, to wait for its completion, and to retrieve the result of the computation. The result can only be retrieved using method get when the computation has completed, blocking if necessary until it is ready. Cancellation is performed by the cancel method. Additional methods are provided to determine if the task completed normally or was cancelled. Once a computation has completed, the computation cannot be cancelled. If you would like to use a Future for the sake of cancellability but not provide a usable result, you can declare types of the form Future<?> and return null as a result of the underlying task.

Cancellation of a Future need not abruptly terminate its computation. Method cancel causes isCancelled() to return true unless already isDone(); in either case isDone() subsequently reports true. This suppresses execution by an ExecutorService if not already started. There are several options for suppressing unnecessary computation or unblocking a running Future that will not generate a result. When task bodies are simple and short, no special attention is warranted. Computational methods in Future-aware code bodies (for example ForkJoinTask, FutureTask) may inspect their own isDone() status before or while engaging in expensive computations. In blocking I/O or communication contexts, the optional mayInterruptIfRunning argument of cancel may be used to support conventions that tasks should unblock and exit when Thread.interrupted, whether checked inside a task body or as a response to an InterruptedException. It is still preferable to additionally check isDone() status when possible to avoid unintended effects of other uses of Thread.interrupt().

Sample Usage (Note that the following classes are all made-up.) interface ArchiveSearcher { String search(String target); } class App { ExecutorService executor = ...; ArchiveSearcher searcher = ...; void showSearch(String target) throws InterruptedException { Callable<String> task = () -> searcher.search(target); Future<String> future = executor.submit(task); displayOtherThings(); // do other things while searching try { displayText(future.get()); // use future } catch (ExecutionException ex) { cleanup(); return; } } } The FutureTask class is an implementation of Future that implements Runnable, and so may be executed by an Executor. For example, the above construction with submit could be replaced by: FutureTask<String> future = new FutureTask<>(task); executor.execute(future);

Memory consistency effects: Actions taken by the asynchronous computation happen-before actions following the corresponding Future.get() in another thread.

Since: 1.5 See Also:

Scripting on this page tracks web page traffic, but does not change the content in any way.