Skip to content

[Strict memory safety] Eliminate false cycle when checking nonisolated(unsafe) #79904

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 1 commit into from
Mar 11, 2025

Conversation

DougGregor
Copy link
Member

When checking for nonisolated(unsafe), don't evaluate the full isolation of the entity, because doing so causes a reference cycle.

…d(unsafe)

Whenc hecking for nonisolated(unsafe), don't evaluate the full isolation
of the entity, because doing so causes a reference cycle.
@DougGregor
Copy link
Member Author

@swift-ci please smoke test

@DougGregor DougGregor enabled auto-merge March 11, 2025 06:00
@DougGregor
Copy link
Member Author

@swift-ci please smoke test macOS

1 similar comment
@DougGregor
Copy link
Member Author

@swift-ci please smoke test macOS

@DougGregor DougGregor merged commit fed1a74 into swiftlang:main Mar 11, 2025
3 checks passed
@DougGregor DougGregor deleted the unsafe-concurrency-cycle branch March 11, 2025 19:56
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.

1 participant