10 ms·
And compilers are effectively a rudimentary form of test. They are not sufficient, nor necessary but they do validate some basic assumptions about the code.
by jsight 7y ago
And compilers are effectively a rudimentary form of test. They are not sufficient, nor necessary but they do validate some basic assumptions about the code.
- mixedCase 7y agoThey also remove redundant testing (you only need to prove something fulfills certain properties once as long as you have a type for it); and the more advanced the type system the fewer tests needed.
- valand 7y agofriendly tips: runtime type checks are available https://github.com/gcanti/io-ts https://github.com/gcanti/io-ts https://github.com/pelotom/runtypes https://github.com/pelotom/runtypes
- paulcowan1970 7y agoI mention io-ts https://github.com/gcanti/io-ts https://github.com/gcanti/io-ts in the post
- valand 7y agoThanks for the article It sparked useful discussion around the world
- valand 7y agoI would upvote you twice if I can for that compiler is a test thing
- thrower123 7y agoIf for no other reason, I would like Typescript for flagging when you typo some property - e.g. foo.FooID vs foo.FooId. I've lost a stupid amount of time in regular JS because of things like this that make me want to pick up the computer and throw it out the window.
- valand 7y agoDecent editor does that now. I'm using atom on daily basis and it's helping me with that. VScode and intellij does the same
- dragonwriter 7y agoDoesn't the functionality for that in most editors leverage typescript typings, so that it's not really independent of typescript?
- valand 7y agoAh I misread the parent comment. I thought it was more like "I wish typescript has this anti-typo functionality" You're right that it's not independent from TS.
- amatecha 7y agoyou can add JSDoc annotations and use a modern IDE like vscode or webstorm, etc.