[5.10][SE-0331][stdlib] Mark unsafe pointer conformances to Sendable as explicitly unavailable #69136
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 please test |
hborla
approved these changes
Oct 11, 2023
|
@swift-ci please test |
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.
Cherry-pick of #69114
This is a preferred way to make sure that Sendable inference doesn't
happen for these types (as described in SE-0331) because they are
marked as
@frozen.Scope: Passing unsafe pointers across concurrency domains.
Main Branch PR: [SE-0331][stdlib] Mark unsafe pointer conformances to Sendable as explicitly unavailable #69114
Resolves: rdar://101980108
Risk: Low
Reviewed By: @ktoso @hborla
Testing: added test-cases to the test suite.