-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Go 5 levels deep when determining if an object type is deeply nested #56140
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
Conversation
Fixes microsoft#56138, but at what cost...
@typescript-bot test this |
Heya @RyanCavanaugh, I've started to run the tarball bundle task on this PR at df4b02a. You can monitor the build here. |
Heya @RyanCavanaugh, I've started to run the diff-based top-repos suite (tsserver) on this PR at df4b02a. You can monitor the build here. Update: The results are in! |
Heya @RyanCavanaugh, I've started to run the diff-based user code test suite on this PR at df4b02a. You can monitor the build here. Update: The results are in! |
Heya @RyanCavanaugh, I've started to run the diff-based user code test suite (tsserver) on this PR at df4b02a. You can monitor the build here. Update: The results are in! |
Heya @RyanCavanaugh, I've started to run the parallelized Definitely Typed test suite on this PR at df4b02a. You can monitor the build here. Update: The results are in! |
Heya @RyanCavanaugh, I've started to run the regular perf test suite on this PR at df4b02a. You can monitor the build here. Update: The results are in! |
Heya @RyanCavanaugh, I've started to run the diff-based top-repos suite on this PR at df4b02a. You can monitor the build here. Update: The results are in! |
Hey @RyanCavanaugh, I've packed this into an installable tgz. You can install it for testing by referencing it in your
and then running There is also a playground for this build and an npm module you can use via |
@RyanCavanaugh Here are the results of running the user test suite comparing Everything looks good! |
@RyanCavanaugh Here are the results of running the user test suite comparing There were infrastructure failures potentially unrelated to your change:
Otherwise... Everything looks good! |
@RyanCavanaugh Here they are:
CompilerComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
tsserverComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
StartupComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
Hey @RyanCavanaugh, it looks like the DT test run failed. Please check the log for more details. |
FWIW DT failed because it ran before we could merge the big refactor there (not sure if that was a factor in you dropping this) |
xstate perf 🫠 |
oh eek well, that's xstate vOld so maybe it'd be better later (new perf when, @jakebailey) |
@RyanCavanaugh Here are the results of running the top-repos suite comparing Everything looks good! |
1 similar comment
@RyanCavanaugh Here are the results of running the top-repos suite comparing Everything looks good! |
Fixes #56138, but at what cost?