-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a proposal to change the execution semantics of nonisolated async functions. #2572
base: main
Are you sure you want to change the base?
Conversation
an async function executes.
aa7ca5a
to
5c48918
Compare
@MainActor let global: NotSendable = .init() | ||
|
||
@MainActor | ||
func callSendableClosure(closure: @Sendable (NotSendable) async -> Void) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this function signature should be changed to:
func callSendableClosure(_ closure: @Sendable (NotSendable) async -> Void) async
`nonisolated` regardless of whether it's applied to synchronous or | ||
async functions. | ||
2. It's important to have an explicit, easy-to-write spelling for async | ||
functions that run on the caller's actor. For example, this is useful to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this say 'run off' or 'do not run on'?
No description provided.