he/him 
FWIW TypeScript's failure modes tend to produce { } instead of 'any'. An 'any' coming out of an expression that didn't start with one is almost always considered a bug
TypeScript Users: How often do you encounter implicit any introduced by the type system? Not the introduction by user code, but the type system returning any for something it shouldn’t.
-
-
-
Any reason it doesn't produce `unknown`?
- 1 more reply
New conversation -
-
-
This Tweet is unavailable.
-
I’d categorise that as user code. I’m talking about the type system getting confused, or just supporting a feature poorly and returning any.
End of conversation
-
-
-
Is there anything that surfaces it when it occurs? IDE hints? Debugging something that should error? Linting?
- 1 more reply
New conversation -
-
Care providing an example?
-
In Flow there's utility types which will often return `any` if it can't figure out the resulting type, making them extremely unpredictable. Same goes for object spread sometimes, and others. https://flow.org/en/docs/types/utilities/ …
- 1 more reply
New conversation -
-
-
Not at all, thanks to --noImplicitAny!
- 13 more replies
New conversation
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.