Post

What if TypeScript had an `unsafe` keyword and `as`, ‘any`, and `!` were only available inside of blocks declared as `unsafe`?

Philippe Serhal@philippeserhal.com

TypeScript RFC: `as` → `unsafe_as` `any` → `unsafe_any` `!` → `!!!` and a tsconfig strict flag to disallow each (I know linters support this already!)

24/7/26, 12:48 pm1 repost12 likes

Marshall Bowers

@maxdeviant.com

24 July

And I guess for `any` in the parameter list or return type you gotta mark it as `unsafe function`.

Brett

@brett.ooo

24 July

You could disallow any in function arguments and then you’d use unknown and cast as any in the unsafe block

claas

@claas.dev

24 July

I think it might be fine to still have any and unknown as types for parameters but as soon as you want to do something with them like access a property or cast them, you have to put them in an unsafe block. I heard pointers in rust work similar?

holliplex.bsky.social

@holliplex.bsky.social

25 July

I’ve considered writing an ESLint plugin for this many times but never gotten around to it—I suppose in the age of Claude one can Just Do It.