[Accepted] SE-0338: Clarify the Execution of Non-Actor-Isolated Async Functions

Hello Swift Community,

The review of SE-0338 "Clarify the Execution of Non-Actor-Isolated Async Functions" has completed. The Core Team has decided to accept this proposal.

Thank you to everyone who participated in the review and pitch!

Doug Gregor
Review Manager


Which decision core team decided to implement?
Main one - switch non isolated functions enter/return to generic executor.
Or always inherit isolated context from the caller?
Third one looks like overhead with unclear restrictions


The core team accepted the semantics specified by the proposal, which you refer to as the "main one": non-isolated async functions run on the generic executor (which is not associated with any actor).


Thank you