-
Notifications
You must be signed in to change notification settings - Fork 13.2k
Fix33448 #35513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix33448 #35513
Conversation
|
@typescript-bot test this |
|
Heya @ahejlsberg, I've started to run the parallelized Definitely Typed test suite on this PR at 6bc8b12. You can monitor the build here. It should now contribute to this PR's status checks. |
|
Heya @ahejlsberg, I've started to run the extended test suite on this PR at 6bc8b12. You can monitor the build here. It should now contribute to this PR's status checks. |
|
Heya @ahejlsberg, I've started to run the parallelized community code test suite on this PR at 6bc8b12. You can monitor the build here. It should now contribute to this PR's status checks. |
|
Heya @ahejlsberg, I've started to run the perf test suite on this PR at 6bc8b12. You can monitor the build here. It should now contribute to this PR's status checks. Update: The results are in! |
|
@ahejlsberg Here they are:Comparison Report - master..35513
System
Hosts
Scenarios
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The user suite test run you requested has finished and failed. I've opened a PR with the baseline diff from master. |
|
RWC and Community test errors look to be preexisting conditions. |
|
RWC is clean on master. Maybe try syncing the branch and running again? Otherwise the change is real. |
|
Looked at it more closely. The RWC difference is just simple error message change because we now pick a different (and arguably better) union constituent to elaborate. |
| (<TransientSymbol>prop).isDiscriminantProperty = | ||
| ((<TransientSymbol>prop).checkFlags & CheckFlags.Discriminant) === CheckFlags.Discriminant && | ||
| isDiscriminantType(getTypeOfSymbol(prop)); | ||
| !maybeTypeOfKind(getTypeOfSymbol(prop), TypeFlags.Instantiable); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the justification for not maybe instantiables here? Previously it was "not generic indexes", so this is quite a bit broader an exclusion, if I'm not mistaken.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you look at isGenericIndexType you'll see that it's more than just generic index types. The code change just clarifies what's actually going on, there's no change in behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh, alright, so it's equivalent. Neat.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we also need to apply/extended similar logic to conditionals in some way? Like if I have a
(T extends U ? { type: "a" } : { type: "b" }) & { type: "b" }, shouldn't it be similarly simplified (at least outside of when infer variables are present)?
Fixes #33448. Also fixes the issue in #33498 (comment).
This PR supercedes #33498. (Thanks @jack-williams!)