I've worked with Typescript for 4 years now on large and small projects, creating my own custom types and using typed and untyped libraries.
I've never run into a case where I had an infinite loop that caused a stack overflow of the Typescript language service or compiler.
I'm not saying it can't happen, but, based on my personal experience, I can't see this as being a "con" for the language.
I can make any compiler blow up with specially crafted code - that's just programming.
If your types are getting very long (I'm assuming because of complex generics), then you can use type aliases to rename them to something shorter...
Or maybe your system complexity is showing itself in the type annotations.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've worked with Typescript for 4 years now on large and small projects, creating my own custom types and using typed and untyped libraries.
I've never run into a case where I had an infinite loop that caused a stack overflow of the Typescript language service or compiler.
I'm not saying it can't happen, but, based on my personal experience, I can't see this as being a "con" for the language.
I can make any compiler blow up with specially crafted code - that's just programming.
If your types are getting very long (I'm assuming because of complex generics), then you can use type aliases to rename them to something shorter...
Or maybe your system complexity is showing itself in the type annotations.