Hi everyone. The review of SE-0564, Split Continuations, ran from November 4 through November 18, 2026, and the Language Steering Group has decided to accept the proposal.
Reviewers agreed that this is a much-needed improvement to the existing withContinuation mechanism for manually suspending and enqueuing a task. The review discussed the possibility of changing the name of the new "split" variant of withContinuation in order to avoid overloading the name. However, we foresee the new variant as being a strict improvement over the previous withContinuation and becoming the preferred API for suspending a task, so it makes sense for it to get the "good" name for the API. There are imminent type checker improvements coming that should mitigate the compile time overhead of resolving call sites as well. As such, the Language Steering Group accepts the proposal as written.
There was some discussion of whether the with- shape is still necessary, and whether the handle and waiter could be even further separated as done with AsyncStream. As the authors noted, the withContinuation API shape is still necessary to allow for the operation to proceed with only stack discipline allocations out of the task context, minimizing the overhead of the primitive.
Thank you to everyone who contributed to the review!
Joe Groff
Review Manager