Avoid erasing type objects when checking runtime cover #19320
+23
−1
Conversation
This file contains hidden or 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
In particular, avoid erasing CallableType that represent type objects Helps with python#19159
This comment has been minimized.
This comment has been minimized.
JukkaL
reviewed
Jun 21, 2025
| @@ -2106,7 +2106,8 @@ def covers_at_runtime(item: Type, supertype: Type) -> bool: | |||
| supertype = get_proper_type(supertype) | |||
|
|
|||
| # Since runtime type checks will ignore type arguments, erase the types. | |||
| supertype = erase_type(supertype) | |||
| if not isinstance(supertype, CallableType): | |||
There was a problem hiding this comment.
Should we only skip erase if the callable type represents a type object? What about overloaded callable types?
|
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.
In particular, avoid erasing CallableType that represent type objects
Helps with #19159