he/him 
I hate the phrase “this isn’t type-safe” when what it really means is “our type system is too restrictive, or not expressive enough”
Show this thread
-
As a person who has done some language design the calculus isn’t whether something’s possible. It’s whether the new capability provides enough value to justify the associated cost of implementation and/or impact to the community to go through a deprecation cycle.
I don't think I roll implementation complexity into my analysis of something being type-safe. Although I understand that's my bias as mostly an observer.
