Various fixes for @preconcurrency
#73698
Merged
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.
Audit the places where we do
Sendable
checking to ensure that they handle@preconcurrency
appropriately, and fix several issues:@Sendable
methods on a non-Sendable
typeSendable
nonisolated let
Sendable
instance properties of an actor-isolated type within the deinitializerMoreover, make sure that we correctly check for
@preconcurrency
for the actual non-Sendable nominal types that occur within a larger type expression, e.g., theNS
inNS?
rather than only looking at the outer optional. This makes@preconcurrency
work properly for arrays, optionals, sets, etc. of non-Sendable
types. Fixes rdar://125081249