-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Concurrency] Remove _unsafeInheritExecutor from public APIs, use #isolation #72578
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
[Concurrency] Remove _unsafeInheritExecutor from public APIs, use #isolation #72578
Conversation
Unblocked by #72813 |
7c63adf
to
bf27392
Compare
Now this still needs some work about backdeployed + unavailable in embedded I think, otherwise it'd be good to go |
f5aea30
to
5e63b09
Compare
@swift-ci please smoke test |
So it turns out solving this issue took a few fixes in related language features and quite some time, but the hackathon is where we kicked off the diagnosis and fixes, so I'd like to thank you @kntkymt for collaborating on this back then! |
5e63b09
to
1bd0463
Compare
@swift-ci please smoke test |
We should be using the
#isolation
macro in all APIs where_unsafeInheritExecutor
was used before;This handles it just for the continuation APIs, more to follow soon.
resolves rdar://125307764
resolves #69659
It seems it runs into availability issues though?
where the unsafe is: