Skip to content

[concurrency] Behind the flag UnspecifiedMeansMainActorIsolated, try inferring by default main actor isolation instead of nonisolated for unspecified. #76558

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

Merged

Conversation

gottesmm
Copy link
Contributor

Just to play with.

…inferring by default main actor isolation instead of nonisolated for unspecified.

Just to play with.
@gottesmm
Copy link
Contributor Author

@swift-ci smoke test

@ktoso
Copy link
Contributor

ktoso commented Sep 19, 2024

I'd be pretty concerned about this mode becoming the default "as is", we'd turn of a lot of parallelism in the system 🤔
But PR itself to just play around with and get a feel for the tradeoffs sure LGTM.

@gottesmm gottesmm merged commit fb28133 into swiftlang:main Sep 19, 2024
3 checks passed
@gottesmm gottesmm deleted the pr-39b63781333d46b16f086a7c192efc67b26255db branch September 19, 2024 16:18
shahmishal pushed a commit that referenced this pull request Sep 23, 2024
Two test using an experimental feature UnspecifiedMeansMainActorIsolated
are not marking as `REQUIRES: asserts` and are failing when asserts are
disabled.

Introduced in #76558
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants