2 ms·
> If the answer is 'testing' then types are indeed an obvious gap in the language Will you not be testing your code anyways? Will you not have unit tests and i
by didibus 6y ago
> If the answer is 'testing' then types are indeed an obvious gap in the language
Will you not be testing your code anyways? Will you not have unit tests and integ tests and have it run in a devo environment first? Before going to production?
If so, then what would the gap be? If you catch those same type errors as you test, and you will be testing anyways?
- loxs 6y agoDepending on the project, I have (not) done all of these and given adequate system (mostly types) design, it's been absolutely OK.
- lttlrck 6y agoSurely catching the errors early is a benefit, or are all typed languages doing it wrong?
- didibus 6y agoIs your argument for it being a benefit that there are lots of languages doing so? Cause there's just as many dynamic languages not doing so, so I'm not sure this argument takes us anywhere.