[ty] Expansion of enums into unions of literals#19382
Merged
Conversation
Contributor
|
Contributor
|
| Lint rule | Added | Removed | Changed |
|---|---|---|---|
invalid-argument-type |
0 | 6 | 0 |
invalid-return-type |
0 | 2 | 0 |
possibly-unresolved-reference |
0 | 2 | 0 |
| Total | 0 | 10 | 0 |
CodSpeed Instrumentation Performance ReportMerging #19382 will not alter performanceComparing Summary
|
07faf92 to
7351142
Compare
9f8c78d to
d8ada59
Compare
carljm
reviewed
Jul 19, 2025
Contributor
carljm
left a comment
There was a problem hiding this comment.
Only got to reviewing the tests so far, but the tests look great!
AlexWaygood
approved these changes
Jul 21, 2025
crates/ty_python_semantic/resources/mdtest/type_properties/is_equivalent_to.md
Show resolved
Hide resolved
Comment on lines
592
to
600
| // Note: we manually construct a `UnionType` here instead of going through | ||
| // `UnionBuilder` because we would simplify the union to just the enum instance | ||
| // and end up in this branch again. | ||
| let db = self.db; | ||
| self.add_positive(Type::Union(UnionType::new( | ||
| db, | ||
| enum_member_literals(db, instance.class.class_literal(db).0, None) | ||
| .collect::<Box<[_]>>(), | ||
| ))) |
Contributor
Author
There was a problem hiding this comment.
Initially, I duplicated what the Type::Union branch does here, but wanted to get rid of that. Fortunately, the wrapping/unwrapping in UnionType doesn't appear to hurt, performance-wise.
dcreager
added a commit
that referenced
this pull request
Jul 22, 2025
* main: (76 commits) Move fix suggestion to subdiagnostic (#19464) [ty] Implement non-stdlib stub mapping for classes and functions (#19471) [ty] Disallow illegal uses of `ClassVar` (#19483) [ty] Disallow `Final` in function parameter/return-type annotations (#19480) [ty] Extend `Final` test suite (#19476) [ty] Minor change to diagnostic message for invalid Literal uses (#19482) [ty] Detect illegal non-enum attribute accesses in Literal annotation (#19477) [ty] Reduce size of `TypeInference` (#19435) Run MD tests for Markdown-only changes (#19479) Revert "[ty] Detect illegal non-enum attribute accesses in Literal annotation" [ty] Detect illegal non-enum attribute accesses in Literal annotation [ty] Added semantic token support for more identifiers (#19473) [ty] Make tuple subclass constructors sound (#19469) [ty] Pass down specialization to generic dataclass bases (#19472) [ty] Garbage-collect reachability constraints (#19414) [ty] Implicit instance attributes declared `Final` (#19462) [ty] Expansion of enums into unions of literals (#19382) [ty] Avoid rechecking the entire project when changing the opened files (#19463) [ty] Add warning for unknown `TY_MEMORY_REPORT` value (#19465) [ty] Sync vendored typeshed stubs (#19461) ...
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
Implement expansion of enums into unions of enum literals (and the reverse operation). For the enum below, this allows us to understand that
Color = Literal[Color.RED, Color.GREEN, Color.BLUE], or thatColor & ~Literal[Color.RED] = Literal[Color.GREEN, Color.BLUE]. This helps in exhaustiveness checking, which is why we see some removedassert_neverfalse positives. And since exhaustiveness checking also helps with understanding terminal control flow, we also see a few removedinvalid-return-typeandpossibly-unresolved-referencefalse positives. This PR also adds expansion of enums in overload resolution and type narrowing constructs.Performance
I avoided an initial regression here for large enums, but the
UnionBuilderandIntersectionBuilderparts can certainly still be optimized. We might want to use the same technique that we also use for unions of other literals. I didn't see any problems in our benchmarks so far, so this is not included yet.Test Plan
Many new Markdown tests