You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi.
As I mentioned in #2997 the fix didn't change anything in my case. I built deeplyNestedTypeArgumentInference branch, copied built/local into my project's typescript/bin and run:
D:\Work\R-n-D\XFW3_WebClient\Client\src>node ..\node_modules\typescript\bin\tsc --module amd --sourceMap -t es5 lib/ui/Part.ts
D:\Work\R-n-D\XFW3_WebClient\Client\node_modules\typescript\bin\tsc.js:0
(function (exports, require, module, __filename, __dirname) { var ts;
^
RangeError: Maximum call stack size exceeded
at new Symbol (D:\Work\R-n-D\XFW3_WebClient\Client\node_modules\typescript\bin\tsc.js)
at createSymbol (D:\Work\R-n-D\XFW3_WebClient\Client\node_modules\typescript\bin\tsc.js:11996:20)
at instantiateSymbol (D:\Work\R-n-D\XFW3_WebClient\Client\node_modules\typescript\bin\tsc.js:15581:26)
at instantiateList (D:\Work\R-n-D\XFW3_WebClient\Client\node_modules\typescript\bin\tsc.js:15475:33)
at instantiateAnonymousType (D:\Work\R-n-D\XFW3_WebClient\Client\node_modules\typescript\bin\tsc.js:15594:33)
at instantiateType (D:\Work\R-n-D\XFW3_WebClient\Client\node_modules\typescript\bin\tsc.js:15613:25)
at instantiateList (D:\Work\R-n-D\XFW3_WebClient\Client\node_modules\typescript\bin\tsc.js:15475:33)
at instantiateType (D:\Work\R-n-D\XFW3_WebClient\Client\node_modules\typescript\bin\tsc.js:15616:61)
at getTypeOfInstantiatedSymbol (D:\Work\R-n-D\XFW3_WebClient\Client\node_modules\typescript\bin\tsc.js:14147:30)
at getTypeOfSymbol (D:\Work\R-n-D\XFW3_WebClient\Client\node_modules\typescript\bin\tsc.js:14153:24)
That is a shame. Unfortunately, without a longer stack trace or a sample that represents the issue, I'm out of ideas. If it is okay for me to see your original source code, I don't mind debugging on that.
This is very similar to #3309. It just uses type argument inference instead of assignability.
The text was updated successfully, but these errors were encountered: