[6.0] Revert "[TypeChecker] TypeChecker::isSubtypeOf should recognize Sendable/@Sendable subtyping" #72877
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 #72868
This approach for ambiguity resolution regressed existing ternary expressions
that join to
any Sendable
and one branch is inferred from the ternary type variable.The test-cases introduced by the original PR I left in place with error messages and
TODOs to figure out a way to resolve ambiguity.
Scope: Ranking solutions where the same type variable gets Sendable and non-Sendable type assignments i.e. ternary expressions where branches are Sendable but contextual type isn't and vice versa.
Main Branch PRs: Revert "[TypeChecker]
TypeChecker::isSubtypeOf
should recognize Sendable/@Sendable subtyping" #72868Risk: Very Low
Reviewed By: @hborla
Testing: Added test-cases to the test suite.