SebastianVerified account

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.

Would love a config that converts all any to undefined, including any cases where TS would infer any to instead infer unknown.

Yesss. I have almost removed all usages of ts-ignore and any/Function/Object in my project. Discovering that the stdlib leaks unsoundness was a bummer.

Adding downcasts don't produce soundness, it just shifts blame

I'm not particularly well versed in proper type system terminology. Where there is any, it produces uncertainness in my code which is why I use a type system in the first place. With proper refinements dealing with unknown is easy and I would prefer extra validation code anyway.

In practice that's really the exception. Most people call JSON.parse and perform ~zero runtime validation on it; they just want to tell the type system what the expected type is. That's equally unsound between 'any' vs downcasted 'unknown'