[ty] Support type[None] in type expressions#22892
Merged
AlexWaygood merged 1 commit intomainfrom Jan 27, 2026
Merged
Conversation
Typing conformance results improved 🎉The percentage of diagnostics emitted that were expected errors increased from 79.08% to 79.11%. The percentage of expected errors that received a diagnostic increased from 70.44% to 70.53%. Summary
True positives addedDetails
|
|
158869b to
b0cfde3
Compare
type[None] in type expressionstype[None] in type expressions
b0cfde3 to
f6c1156
Compare
Member
Author
|
I misread what the conformance suite was asking of us here initially -- and I'm not sure the demands it's making are really correct in this case. But I think there's no harm in supporting this for now. |
carljm
approved these changes
Jan 27, 2026
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
This is mandated by the typing conformance suite.
I'm honestly quite sceptical that it should be mandated by the conformance suite, but that's a battle for another day. It's trivial to support it now, and it'll be trivial to rip it out and emit an error instead at a later date if the spec is amended. Anything is better than that status quo (which is a
@Todotype).Test Plan
mdtests