Fix OR pattern structural matching exhaustiveness
#18119
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
This comment has been minimized.
This comment has been minimized.
shenyih0ng
force-pushed
the
fix/or-pattern-match-exhaustiveness
branch
from
4cd8a8c
to
2c6a179
Compare
This comment has been minimized.
This comment has been minimized.
shenyih0ng
force-pushed
the
fix/or-pattern-match-exhaustiveness
branch
from
2c6a179
to
ff90fbb
Compare
|
According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅ |
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.
Fixes #18108
This PR fixes the issue of missing value comparisons in a
MatchStmtdue toOrPatternincorrectly narrowing down the type of the subject.