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*.
-
-
Replying to @chriskrycho @typescriptlang
Agree with the hugely positive sentiment. Since we're tossing out top issues: - Lack of associated types - Lack of nominal types (what flow calls opaque types) - Error messages (All three affect me daily and would drastically improve my day-to-day)
4 replies 1 retweet 4 likes -
What do u want to see for errors specifically? We have been talking about some improvements but would love to hear what you have in mind.
2 replies 0 retweets 0 likes -
I would like every error to include a link to a page for that diagnostic code where users could contribute explanation and examples of how to fix.
1 reply 0 retweets 2 likes
The bigger problem is that structural typing errors, especially with generics, produce a soup that doesn't usually map cleanly onto what I think I did wrong. Too often the error is just a page of goop.
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.