[6.1][Concurrency] Fix a few issues with matching any Sendable
to Any
#79430
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 #79382 and #78789
Explanation:
Allows
Any
to be matched againstany Sendable
when it appears in generic argument position of a valuepassed as an
inout
argument (both explicit and implicit).Downgrades a few Sendable conformance diagnostics to warnings in Swift 6 mode when base of a member reference or assignment destination are marked as
@preconcurrency
.A minor diagnostic improvement for generic argument mismatch with leading-dot syntax.
Main Branch PRs: [Concurrency] Fix a few issues with
Senable
andAny
#79382 and [Diagnostics] Fix generic arguments mismatch diagnostic related to le… #78789Risk: Low (allows some code that previously was rejected by the compiler to type-check successfully).
Resolves: rdar://144794132
Reviewed By: @hborla
Testing: Added new tests to the Concurrency/SILGen and Interprete test suites.
(cherry picked from commit 00fe563)