[ty] More type-variable default validation#23639
Open
AlexWaygood wants to merge 1 commit intomainfrom
Open
Conversation
Typing conformance resultsNo changes detected ✅ |
|
Memory usage reportMemory usage unchanged ✅ |
Member
Author
|
Following #23623, I guess we now pass all the conformance tests regarding typevar default scoping. But I still think this PR improves semantics -- it matches pyright's behaviour. The upstream tests seem like they're missing some coverage. |
|
af5547b to
c1a2615
Compare
c1a2615 to
8e099a8
Compare
8e099a8 to
2920f62
Compare
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
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.
Summary
We have several checks at the moment which fire on legacy type variables with invalid defaults in a class context, but which fail to check for legacy type variables with invalid defaults in a function context. This PR adds those missing checks.
The typing spec states that both legacy and PEP-695 type variables are not allowed to have defaults that:
The typing spec also states that a type variable with a default is not allowed to come before any type variables without defaults.
Test Plan
mdtests and snapshots