There is a very short list of things I wish @typescriptlang did differently, but at the top, and by a mile is: embracing soundness as an explicit goal.
Soundness empowers developers to be productive, especially in the long life of a project: it’s a super-power for *refactoring*.
-
-
I can imagine all the hackish things we'd have to do just to get things work as if we had them.
-
I’m jazzed to see what happens as we land generic associated types. Should unlock an awful lot of interesting things.
-
I have a real nice FSM pattern I want to try with that and impl Trait in Trait
-
What do you mean by FSM? (I can’t read that and come up with anything but “Flying Spaghetti Monster.”
) -
Finite State Machine?
-
Yes, that, there we go. It is definitely Friday night.

-
Also I may or may not be over here building out as small as possible a reproduction for a place where TS’ type system just… gives up. It actually *behaves* like Rust’s not having traits in scope problem, in that it fails to resolve a given type without import. But no error.
End of conversation
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.