Skip to content
Better HN
Top
New
Best
Ask
Show
Jobs
Search
⌘K
undefined | Better HN
0 points
arjie
11y ago
0 comments
Share
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.
0 comments
default
newest
oldest
Touche
11y ago
I disagree, tests and QA happens regardless. Adding a compile step to development is a big downside to the type approach.
j
/
k
navigate · click thread line to collapse