Adopt noasync for ThreadSpecificVariable
#2206
Merged
Conversation
This file contains 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
dnadoba
added
the
🔼 needs-minor-version-bump
Lukasa
reviewed
Jun 29, 2022
|
@swift-nio-bot test this please |
1 similar comment
|
@swift-nio-bot test this please |
Lukasa
approved these changes
Jun 30, 2022
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.
Mark
ThreadSpecificVariable.currentValueas not available from asynchronous context.Motivation:
From SE-0340 (Unavailable From Async Attribute):
Modifications:
add
@available(*, noasync)toThreadSpecificVariable.currentValuein Swift 5.7+Result:
Prevent accidental misuse of
ThreadSpecificVariableNote: The
noasyncdiagnostics in the latest Swift 5.7 nightly compiler emits errors instead of warnings but this is already fixed and will be part of the next 5.7 nightly toolchain. swiftlang/swift#59748