I'm shocked at how often I run into problems due to TypeScript's generous usage of `any` in the standard library definitions. `unknown` is much more appropriate. The promotion of escaping type safety in such a fundamental place is worrying.
-
-
I'd like to see an example - this shouldn't be possible with noImplicitAny on
-
This produces no errors with noImplicitAny even though `foo` has been refined to `Array<any>` ``` const foo: unknown = []; if (Array.isArray(foo)) { foo; } ```
- 1 more reply
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.
he/him 