Skip to content

[Concurrency] Fix nonisolated(nonsending) interaction with #isolation #82793

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

Conversation

ktoso
Copy link
Contributor

@ktoso ktoso commented Jul 4, 2025

This was noticed early on, but we never fixed it.

This makes #isolation actually find the isolated parameter that nonisolated(nonsending) implicitly adds to functions.

Resolves rdar://155003540

@ktoso
Copy link
Contributor Author

ktoso commented Jul 4, 2025

@swift-ci please smoke test

@ktoso
Copy link
Contributor Author

ktoso commented Jul 7, 2025

Moved the check and added a SIL test, thanks for review @DougGregor 👍

@ktoso ktoso force-pushed the wip-correct-isolated-handling-with-caller-isolation branch from a6b4b5b to b1ca06d Compare July 7, 2025 02:37
@ktoso
Copy link
Contributor Author

ktoso commented Jul 7, 2025

@swift-ci please smoke test

@ktoso ktoso added the concurrency Feature: umbrella label for concurrency language features label Jul 7, 2025
@ktoso ktoso merged commit c6f223f into swiftlang:main Jul 8, 2025
3 checks passed
@ktoso ktoso deleted the wip-correct-isolated-handling-with-caller-isolation branch July 8, 2025 03:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
concurrency Feature: umbrella label for concurrency language features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants