This is such a nerd tweet lol
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Is this related to not being able to use the regexp types suggestion u posted in the past?

-
It's not. More general about type systems claiming something isn't type-safe when it's actually the type system not being smart enough. The argument becomes centered around fitting into the existing system rather than how the system can change to accommodate.
- 2 more replies
New conversation -
-
-
From the other side, the conversation sounds like this: > "This function isn't type-safe, if you called it like (this), it would crash/corrupt data" < "Sure, but we don't call it that way right now, so there's no problem"
-
That's not exactly what my tweet meant. I'm referring to type system authors using the term "not type-safe" when they're actually referring to their own technical capabilities, rather than what would be technically possible
End of conversation
New conversation -
-
-
Personally the majority of the time I've heard this said, at least with TypeScript, was because of a lack of understanding of the type system or a lack of time investment in implementing it the "right" way.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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 