Skip to content

[concurrency] Introduce concurrent, swap its meaning with nonisolated and make nonisolated caller inheriting isolation. #79087

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
merged 4 commits into from
Feb 4, 2025

Conversation

gottesmm
Copy link
Contributor

Just a refactoring to make the semantics line up.

Copy link
Contributor

@xedin xedin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about new #pragma but otherwise LGTM!

@gottesmm gottesmm force-pushed the actor-isolation-refactoring branch from 9c79acf to 2ed1e9e Compare February 3, 2025 18:54
…ctorIsolation::Nonisolated.

This is just the first part of a larger transition.
…riting and delete CallerIsolationInheriting.
This ensures it works for both nonisolated(unsafe) and concurrent(unsafe).
@gottesmm gottesmm force-pushed the actor-isolation-refactoring branch from 2ed1e9e to 95623c6 Compare February 3, 2025 18:56
@gottesmm
Copy link
Contributor Author

gottesmm commented Feb 3, 2025

@swift-ci smoke test

@gottesmm gottesmm enabled auto-merge February 3, 2025 19:00
@gottesmm
Copy link
Contributor Author

gottesmm commented Feb 3, 2025

@swift-ci smoke test

@gottesmm gottesmm merged commit 342bbd3 into swiftlang:main Feb 4, 2025
3 checks passed
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