You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
TypeScript Design Goals - Non-Goals: "Non-goal 3: Apply a sound or "provably correct" type system. Instead, strike a balance between correctness and productivity."
The text was updated successfully, but these errors were encountered:
I've included an example on soundness in microsoft/TypeScript-Website#43 which I think is probably enough, it doesn't aim to be comprehensive but it explains what soundness is, why TS isn't sound, provides examples and then links to the two main places where it is documented.
I think I would still suggest documenting and publicizing this more openly than an example - feels like having this in the top-level handbook documentation would help clear up a lot of things for beginners and experienced developers alike.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From my tweet, where I suggested that it would be beneficial to have a Handbook page on Soundness:
https://twitter.com/karlhorky/status/1146687994142842880
My initial top-of-my-head suggestions in the tweet were to include at least the following information:
Happy to add to the list, if anyone thinks of anything!
Unsound Behaviors
For 2. above, starting a list of unsound behaviors here:
No excess property checks in object types with spread (Playground)
Incorrect definition of spread and Object.assign (Playground)
Trade-offs in Control Flow Analysis
This has been prompted by the high-quality criticisms as of late on Twitter by @sebmck:
This has been going on since ~ June 18:
Articles / discussion on the topic:
The text was updated successfully, but these errors were encountered: