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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need the third "fallback" overload, as the other overloads already cover all possible cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried that, and mypy needs the third overload. With only the two
Literaloverloads, passing a plainboolvariable fails:Pyright expands
boolintoLiteral[True] | Literal[False]during overload resolution, but mypy does not, so the literal overloads alone do not cover every call. With the fallback restored, the same call resolves to the union and all four call shapes check out.This matches what typeshed already does elsewhere for the same situation, for example
ssl.SSLObject.getpeercertand_winapi.ConnectNamedPipe, which both keep a trailingbooloverload after the two literal ones.Happy to drop it if you would rather have the stricter signature, but that would be a small regression for callers who pass a computed flag.