Work in Progress CallableType usingpretty_callable_or_overload #19027
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
Contributor
|
According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅ |
Collaborator
|
Feel free to re-open if you complete this and get CI passing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Objective
Refactor the generation of error messages involving CallableType by using pretty_callable_or_overload(...) to improve clarity and consistency, as discussed in issue #5490.
Changes Made
Refactored the pos, invert, call, and other related blocks.
Replaced calls to format_type(...) with conditional logic that uses pretty_callable_or_overload(...) when applicable.
Added a test case in operators.test to verify the new message formatting.
Tests
Ran with pytest, and all tests passed successfully.