Hi Swift Evolution!
The third review of SE-0300 — Continuations for interfacing async tasks with synchronous code begins now and runs through March 9, 2021.
Following the second review of this proposal, the core team feels that the proposal is close to acceptance, and is an important feature as part of Swift's concurrency roadmap. However, a small number of amendments have been made based on feedback during the second review.
- Replaced separate
*ThrowingContinuation<T>types with a
Continuation<T, E: Error>type parameterized on the error type.
- Added a convenience
continuations with a
with*ThrowingContinuationto take an
operationblock that may
throw, and to immediately resume the task throwing the error if an uncaught
error propagates from the operation
Reviews are an important part of the Swift evolution process. All review feedback should be either on this forum thread or, if you would like to keep your feedback private, directly to the review manager (via email or direct message in the Swift forums).
What goes into a review of a proposal?
The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of Swift.
When reviewing a proposal, here are some questions to consider:
- What is your evaluation of the proposal?
- Is the problem being addressed significant enough to warrant a change to Swift?
- Does this proposal fit well with the feel and direction of Swift?
- If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
- How much effort did you put into your review? A glance, a quick reading, or an in-depth study?