Defer simplification of conditionals on deferred type references #37423
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.
Fixes #37344
When we started "normalizing" deferred type aliases at the start of comparisons (#35266), we started to eagerly pull on them when we constructed conditional types around them (as conditionals eagerly check to see if they can simplify to their branches in some cases), which means that that normalization actually broke some very common patterns (like the generic action alias in the linked issue). To avoid that break, while still performing that normalization, in this PR, we now unconditionally defer conditionals where the check or extends type is itself a deferred type reference, and then later on perform the simplification of the conditional as part of
getReducedType
(introduced in #36696), so that deferral isn't witnessed by most consumers of the type.