Repository navigation
fix: do not emit variance-mismatch for constrained typevars in protocols #5500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Aayushyaash
wants to merge
4
commits into
meta:main
from
Aayushyaash:fix-variance-mismatch-constrained-typevar
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
6154fed
test: add regression test for constrained typevar in protocol
Aayushyaash 3fe3b04
fix: do not emit variance-mismatch for constrained typevars in protocols
Aayushyaash 6976056
Merge branch 'meta:main' into fix-variance-mismatch-constrained-typevar
Aayushyaash e579257
fix: update conformance outputs and refine constrained typevar comment
Aayushyaash File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
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.
Curious about the asymmetry with
Restriction::Explicit(bounded) TypeVars:protocols_variance.py/ the conformance report presumably still flags invariant bounded TypeVars as variance-mismatch (e.g.T = TypeVar("T", bound=X)used covariantly). Was the noise argument applied only to constrained TypeVars because a bounded TypeVar can soundly narrow its variance within the bound, or is this an intentional first step? If bounded TypeVars are also usually noise for this warning, the doc comment here might merit one sentence explaining why Constraints gets the carve-out rather than Explicit.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.
The argument (originally from @DetachHead) is that variance is generally irrelevant to constrained type variables, because a constrained type variable solves to exactly one of its bounds.
As a result, subtyping is almost irrelevant (if the types are not subtypes of one another, like
(str, bytes)), which makes variance irrelevant (in the sense that absent subtyping, variance doesn't even exist as a concept - for example Haskell and OCaml and Rust have and require no notion of variance) and means this warning produces unnecessary noise.The argument is heuristic because it's possible to use a constrained type variable whose options are orderable in the type system, for example I've seen
(int, float)before. In that case variance is technically still meaningful.