Always discriminate contextual types by existing discriminant property#61097
Open
Andarist wants to merge 1 commit intomicrosoft:mainfrom
Open
Always discriminate contextual types by existing discriminant property#61097Andarist wants to merge 1 commit intomicrosoft:mainfrom
Andarist wants to merge 1 commit intomicrosoft:mainfrom
Conversation
Member
|
@typescript-bot test it |
Collaborator
Collaborator
|
@jakebailey Here are the results of running the user tests with tsc comparing Everything looks good! |
Collaborator
|
Hey @jakebailey, the results of running the DT tests are ready. There were interesting changes: Branch only errors:Package: knockout Package: react-dates |
Collaborator
|
@jakebailey Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Collaborator
|
@jakebailey Here are the results of running the top 400 repos with tsc comparing Something interesting changed - please have a look. Details
|
jakebailey
reviewed
Feb 22, 2025
| return false; | ||
| } | ||
| if (p.kind === SyntaxKind.PropertyAssignment) { | ||
| return isPossiblyDiscriminantValue(p.initializer) && isDiscriminantProperty(contextualType, p.symbol.escapedName); |
Member
There was a problem hiding this comment.
I feel like it's at least moderately concerning that this leaves the code with only one use of isPossiblyDiscriminantValue; shouldn't it be the case that if isPossiblyDiscriminantValue returns false, isDiscriminantProperty should have also returned false?
The documentation for isPossiblyDiscriminantValue implies that it's there to avoid circularities, so I'm surprised that it is a problem, and that we aren't somehow introducing circularities by not calling it anymore...
But even more surprisingly, if you just straight up delete isPossiblyDiscriminantValue and its one use (so, make it so that it always returns true), no test fails.
Contributor
Author
There was a problem hiding this comment.
The documentation for isPossiblyDiscriminantValue implies that it's there to avoid circularities, so I'm surprised that it is a problem, and that we aren't somehow introducing circularities by not calling it anymore...
It may not be about circularities in the form of implicit any. One of the failures here is related to a code like this:
interface KnockoutObservable<T> {
(value: T): void;
}
interface KnockoutObservableStatic {
<T>(value: T): KnockoutObservable<T>;
}
interface KnockoutObservableArrayStatic {
<T>(value: T[]): KnockoutObservable<T>;
}
interface KnockoutStatic {
observable: KnockoutObservableStatic;
observableArray: KnockoutObservableArrayStatic;
}
declare var ko: KnockoutStatic;
ko.observableArray([
{ someProp: 1 },
{ someProp: 2, _destroy: "evals to true" },
{ someProp: 3 },
{ someProp: 4, _destroy: ko.observable(false) },
]);At the moment, the inner ko.observable has a resolving signature - that is temporarily set on it during inference. Requesting its type here changes that prematurely or smth like that. I haven't yet had time to investigate this further to see what I could do to mitigate this problem though.
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
4 participants
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 #58508
fixes #61095
I think the added
tests/cases/compiler/contextuallyTypedByDiscriminableUnion2.tstest case tells it all (TS playground). Currently both property assignments that reference external values and shorthand property assignments are capable of narrowing this case but a property assignment with an "inline" initializer isn't.