2 ms·
The point is that you substitute the extra testing and QA with types. The assertion doesn't guarantee type correctness, so you test that function and downstream
by arjie 12y ago
The point is that you substitute the extra testing and QA with types. The assertion doesn't guarantee type correctness, so you test that function and downstream functions. That's extra code burden. Instead, you could have type checking.
- Touche 12y agoI disagree, tests and QA happens regardless. Adding a compile step to development is a big downside to the type approach.