-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can you talk about: Type safety? #193
Comments
I can talk about TypeScript and the benefits and drawbacks. I've been using it since 0.8 back in 2012. |
I can talk about type systems. Is there a specific focus you have in mind? |
Higher-Kinded Types in TypeScript! |
I think an introduction to types and the benefits / drawbacks - out of date type definitions for non-TS deps, or changes to upstream types that break things (an example) come to mind. With those kind of errors you end up losing time fixing things that add no direct business value. Identifying bugs like failure to return a value from a function, or returning the wrong thing (incl. not awaiting a Promise), non-exhaustive switches etc is a benefit. As is an ergonomic surface for code (self-documenting) including drop-downs for discriminated unions of string literals. Use boolean literals to create type guards which cast inside blocks is also very cool. |
No description provided.
The text was updated successfully, but these errors were encountered: