GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||
GeezerVison is showing github.com — Add maxInstantiationDepth to compiler optionDeclarations by AnyhowStep · Pull Request #29602 · microsoft/TypeScript Conversation
|
|
maxInstantiationDepth is an intentional limitation of the compiler to prevent slow compiles, so we're not going to remove it. Even if #32611 allows much more nested types to compile, it's likely that we'll have a different kind of limiter in place. Because that future limiter will be named something different, I don't think PR will apply to it. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
I am surprised by the feedback; TypeScript's flexibility has always been its strength. If a codebase and an engineering team feel it could benefit more from a complex typing structure that enables something that may not be otherwise enabled with full compile time type safety; why shouldn't they be empowered to make the tradeoff choice themselves about whether they will accept slow compiles? Especially when the change seems so easy and clean. Perhaps there is more to the story than I see though; would you be open to further discussion? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
[API Question] Is there a type resolution depth limit difference between compiling and running the language service?
There was an error while loading. Please reload this page.