[6.1][CSApply] Sendable-to-Any: Add support for l-value to l-value and inout unsafe casts #78492
+198
−23
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 #78487
Explanation:
Extends functionality of
any Sendable
->Any
conversion ingeneric argument positions to support subscripts and mutating accesses.
This means that we cannot reply on simple type equality in some
cases i.e. when applying base to
self
parameter. If type equalitycheck fails we need to check whether the types are the same with
deep equality restriction since
any Sendable
toAny
conversionis now supported in generic argument positions of
@preconcurrency
declarations. i.e. referencing a member on
[any Sendable]
if memberdeclared in an extension that expects
Element
to be equal toAny
.Main Branch PR: [CSApply] Sendable-to-Any: Add support for l-value to l-value and inout unsafe casts #78487
Resolves: rdar://140300022
Risk: Low (Extends functionality of the previous PR - [6.1][TypeChecker/SILGen] Allow
any Sendable
to matchAny
while matching generic arguments #78272 to support subscripts and mutating accesses).Reviewed By: @hborla
Testing: Added new tests to the concurrency, SILGen, and interpreter test suites.