-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Fix recursive type inference #53396
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
Fix recursive type inference #53396
Conversation
@typescript-bot test this |
Heya @ahejlsberg, I've started to run the diff-based user code test suite on this PR at cd7165c. You can monitor the build here. Update: The results are in! |
Heya @ahejlsberg, I've started to run the diff-based top-repos suite on this PR at cd7165c. You can monitor the build here. Update: The results are in! |
Heya @ahejlsberg, I've started to run the extended test suite on this PR at cd7165c. You can monitor the build here. |
Heya @ahejlsberg, I've started to run the abridged perf test suite on this PR at cd7165c. You can monitor the build here. Update: The results are in! |
Heya @ahejlsberg, I've started to run the parallelized Definitely Typed test suite on this PR at cd7165c. You can monitor the build here. Update: The results are in! |
@@ -249,7 +249,7 @@ declare let z: Box2<Box2<string>>; | |||
>z : Box2<Box2<string>> | |||
|
|||
foo(z); // unknown, but ideally would be string (requires unique recursion ID for each type reference) |
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.
Comment can probably be removed here now that this is saying string
?
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.
Yeah. Neat that we already had a test to show the issue.
@ahejlsberg Here are the results of running the user test suite comparing Everything looks good! |
@ahejlsberg Here are the results of running the top-repos suite comparing Everything looks good! |
Oh, could this also fix what I was working on in #53327? |
Hey @ahejlsberg, the results of running the DT tests are ready. |
@MariaSolOs I doubt it, unfortunately. |
Waiting on the performance suite, everything else looks good. |
@typescript-bot perf test faster |
Heya @ahejlsberg, I've started to run the abridged perf test suite on this PR at 4ce18e0. You can monitor the build here. Update: The results are in! |
The original run is still queued; we just have a huge perf backlog and that's why it hasn't shown up yet. |
@ahejlsberg Here they are:Comparison Report - main..53396
System
Hosts
Scenarios
Developer Information: |
@ahejlsberg Here they are:Comparison Report - main..53396
System
Hosts
Scenarios
Developer Information: |
This PR reverts #49226 and instead fixes the problem as described here.
Fixes #48524.
Fixes #52722.