[ty] Remove redundant apply_specialization type mappings#22422
Merged
dhruvmanila merged 3 commits intomainfrom Jan 7, 2026
Merged
[ty] Remove redundant apply_specialization type mappings#22422dhruvmanila merged 3 commits intomainfrom
apply_specialization type mappings#22422dhruvmanila merged 3 commits intomainfrom
Conversation
Diagnostic diff on typing conformance testsNo changes detected when running ty on typing conformance tests ✅ |
AlexWaygood
approved these changes
Jan 6, 2026
|
ibraheemdev
approved these changes
Jan 6, 2026
dhruvmanila
approved these changes
Jan 7, 2026
Member
dhruvmanila
left a comment
There was a problem hiding this comment.
Thanks! I'll merge this and rebase my PR
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.
@dhruvmanila encountered this in #22416 — there are two different
TypeMappingvariants for apply a specialization to a type. One operates on a fullSpecializationinstance, the other on a partially constructed one. If we move this enum-ness "down a level" it reduces some copy/paste in places where we are operating on aTypeMapping.