A unit of asynchronous work.
- iOS 13.0+
- macOS 10.15+
- tvOS 13.0+
- watchOS 6.0+
@frozen struct Task<Success, Failure> where Success : Sendable, Failure : Error
When you create an instance of
Task, you provide a closure that contains the work for that task to perform. Tasks can start running immediately after creation; you don’t explicitly start or schedule them. After creating a task, you use the instance to interact with it — for example, to wait for it to complete or to cancel it. It’s not a programming error to discard a reference to a task without waiting for that task to finish or canceling it. A task runs regardless of whether you keep a reference to it. However, if you discard the reference to a task, you give up the ability to wait for that task’s result or cancel the task.
To support operations on the current task, which can be either a detached task or child task,
Task also exposes class methods like
yield(). Because these methods are asynchronous, they’re always invoked as part of an existing task.
Only code that’s running as part of the task can interact with that task. To interact with the current task, you call one of the static methods on
A task’s execution can be seen as a series of periods where the task ran. Each such period ends at a suspension point or the completion of the task. These periods of execution are represented by instances of
PartialAsyncTask. Unless you’re implementing a custom executor, you don’t directly interact with partial tasks.
For information about the language-level concurrency model that
Task is part of, see Concurrency in The Swift Programming Language.
Tasks include a shared mechanism for indicating cancellation, but not a shared implementation for how to handle cancellation. Depending on the work you’re doing in the task, the correct way to stop that work varies. Likewise, it’s the responsibility of the code running as part of the task to check for cancellation whenever stopping is appropriate. In a long-task that includes multiple pieces, you might need to check for cancellation at several points, and handle cancellation differently at each point. If you only need to throw an error to stop the work, call the
Task.checkCancellation() function to check for cancellation. Other responses to cancellation include returning the work completed so far, returning an empty result, or returning
Cancellation is a purely Boolean state; there’s no way to include additional information like the reason for cancellation. This reflects the fact that a task can be canceled for many reasons, and additional reasons can accrue during the cancellation process.