Static types: Difference between revisions
From ym2149.org
Jump to navigationJump to search
(Created page with "* weird that params and return types are obsessively typed, but not exceptions * all their stated advantages can be achieved via unit testing, which you need anyway * lightweight mocks redundant in the absence of static types, you can just use the test harness as a universal mock Category:Programming") |
No edit summary |
||
| Line 2: | Line 2: | ||
* all their stated advantages can be achieved via unit testing, which you need anyway | * all their stated advantages can be achieved via unit testing, which you need anyway | ||
* lightweight mocks redundant in the absence of static types, you can just use the test harness as a universal mock | * lightweight mocks redundant in the absence of static types, you can just use the test harness as a universal mock | ||
* a kind of gatekeeping or hazing, you can join the programming club so long as you keep burning energy typing things | |||
[[Category:Programming]] | [[Category:Programming]] | ||
Latest revision as of 12:15, 26 April 2024
- weird that params and return types are obsessively typed, but not exceptions
- all their stated advantages can be achieved via unit testing, which you need anyway
- lightweight mocks redundant in the absence of static types, you can just use the test harness as a universal mock
- a kind of gatekeeping or hazing, you can join the programming club so long as you keep burning energy typing things
