-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Use a single relation stack for nested dependent variance calculations #39232
Use a single relation stack for nested dependent variance calculations #39232
Conversation
@typescript-bot user test this |
Heya @weswigham, I've started to run the parallelized community code test suite on this PR at c9e57e1. You can monitor the build here. |
Heya @weswigham, I've started to run the extended test suite on this PR at c9e57e1. You can monitor the build here. |
Heya @weswigham, I've started to run the parallelized Definitely Typed test suite on this PR at c9e57e1. You can monitor the build here. |
Heya @weswigham, I've started to run the perf test suite on this PR at c9e57e1. You can monitor the build here. Update: The results are in! |
The user suite test run you requested has finished and failed. I've opened a PR with the baseline diff from master. |
@weswigham Here they are:Comparison Report - master..39232
System
Hosts
Scenarios
|
Hm, perf is good, but looks like RWC has an example where the failure to invalidate the |
c9e57e1
to
98a661b
Compare
@typescript-bot user test this This modified fix passes RWC locally, but might have some perf impact, since it utilizes |
Heya @weswigham, I've started to run the extended test suite on this PR at 53a7560. You can monitor the build here. |
Heya @weswigham, I've started to run the parallelized community code test suite on this PR at 53a7560. You can monitor the build here. |
Heya @weswigham, I've started to run the perf test suite on this PR at 53a7560. You can monitor the build here. Update: The results are in! |
Heya @weswigham, I've started to run the parallelized Definitely Typed test suite on this PR at 53a7560. You can monitor the build here. |
The user suite test run you requested has finished and failed. I've opened a PR with the baseline diff from master. |
@weswigham Here they are:Comparison Report - master..39232
System
Hosts
Scenarios
|
Perf looks OK - there's potentially a ~1% difference in |
Tried compiling the project against this branch, but we are still getting this error: /home/nicolas/Development/Programs/Typescript/wollok-ts/node_modules/typescript/lib/typescript.js:43927
function getIsDeferredContext(location, lastLocation) {
^
RangeError: Maximum call stack size exceeded
at getIsDeferredContext (/home/nicolas/Development/Programs/Typescript/wollok-ts/node_modules/typescript/lib/typescript.js:43927:38)
at resolveNameHelper (/home/nicolas/Development/Programs/Typescript/wollok-ts/node_modules/typescript/lib/typescript.js:43585:66)
at resolveName (/home/nicolas/Development/Programs/Typescript/wollok-ts/node_modules/typescript/lib/typescript.js:43521:20)
at resolveEntityName (/home/nicolas/Development/Programs/Typescript/wollok-ts/node_modules/typescript/lib/typescript.js:44744:42)
at resolveTypeReferenceName (/home/nicolas/Development/Programs/Typescript/wollok-ts/node_modules/typescript/lib/typescript.js:52868:20)
at getTypeFromTypeReference (/home/nicolas/Development/Programs/Typescript/wollok-ts/node_modules/typescript/lib/typescript.js:53051:30)
at getTypeFromTypeNodeWorker (/home/nicolas/Development/Programs/Typescript/wollok-ts/node_modules/typescript/lib/typescript.js:54919:28)
at getTypeFromTypeNode (/home/nicolas/Development/Programs/Typescript/wollok-ts/node_modules/typescript/lib/typescript.js:54881:49)
at tryGetTypeFromEffectiveTypeNode (/home/nicolas/Development/Programs/Typescript/wollok-ts/node_modules/typescript/lib/typescript.js:49450:24)
at getTypeForVariableLikeDeclaration (/home/nicolas/Development/Programs/Typescript/wollok-ts/node_modules/typescript/lib/typescript.js:48972:32)
It's has a different stack trace than the one we got on #39059, but seems related. |
Unfortunately, we never finished reviewing this PR. It is pretty old now, so I'm going to close it to reduce the number of open PRs. |
Fixes #39059