[6.2] Revert nonisolated(unsafe) closure inference #83102
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@swift-ci test |
|
@gottesmm this is about |
gottesmm
changed the title
|
@xedin yes. Sorry! My brain failed. |
hborla
approved these changes
Jul 16, 2025
|
Timed out in LLVM |
|
@swift-ci test macOS platform |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description: We were going to try and take this fix for nonisolated(unsafe) closures for 6.2... but decided to delay. This just removes it from 6.2.
Scope/Impact: nonisolated(unsafe) will not be inferred onto anonymous closure literals if the closure has only nonisolated(unsafe) captures.
Risk: Low. This didn't make it out into the world, so no risk.
Testing: CI testing
Reviewed by: N/A
Original PR: N/A
Radar: N/A