Skip to content
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

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

hborla
Copy link
Member

@hborla hborla commented Sep 22, 2024

No description provided.

@MainActor let global: NotSendable = .init()

@MainActor
func callSendableClosure(closure: @Sendable (NotSendable) async -> Void) {
Copy link
Contributor

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

@rjmccall rjmccall added the LSG Contains topics under the domain of the Language Steering Group label Sep 30, 2024
`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
Copy link
Contributor

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'?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LSG Contains topics under the domain of the Language Steering Group
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants