Improve conditional type constraints #23039
Merged
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.
This PR improves our reasoning over constraints associated with conditional types. We now consider a conditional type of the form
T extends U ? T : X
to have the constraint(T & U) | F
(meaning thatT extends U ? T : X
is assignable to anything to which(T & U) | F
is assignable). Previously we considered the constraint to just beT | F
, but we now factor in the relationship toU
that has been proven by theextends
clause.With this change the predefined
Extract<T, U>
conditional type effectively becomes a way of representing a typeT
with an additional constraintU
. Or, in more intuitive terms, aT
that is also known to be aU
. For example:Fixes #22899.