Re:Returning to JavaScript After 5 Years
by ClayFerguson on Sunday January 08, 2017 @11:53AM
(#13350586)
The 'assignability rules' of TS catches type-errors in a way that 'solves' all the problems JS ever had. You can critique the nature of that solution if you want (after all, there are an infinite number of solutions in the solution-set), but I think it's a perfect solution.
Give any good developer TS to code in, and he'll know how to use it to check every type in every variable, class, or method parameter, and the checking will be 100% perfectly reliable. That's what I mean by "problem solved".
Re:Returning to JavaScript After 5 Years
by automatwon on Sunday January 08, 2017 @06:32PM
(#13352782)
Google's closure compiler already addressed that
Re:Returning to JavaScript After 5 Years
by ClayFerguson on Sunday January 08, 2017 @11:09PM
(#13353942)
Yeah, that's what I just said.
A Google query for the definition of unsound: "not safe or robust"
https://www.typescriptlang.org/docs/handbook/type-compatibil...
You're portraying TypeScript as if it's perfect. Typescript is is permissive and structurally, rather than nominally typed. This is not TypeScript's fault. There will always be tradeoffs. Among other things in the FAQ, there is a section on how to prevent two types from being structurally incompatible. "A possible FIX if you really want two types to be incompatible is to add a 'brand' member"...
https://github.com/Microsoft/TypeScript/wiki/FAQ#type-system...