3 ms·
Such an error would be immediately obvious on code review. The idea is to make it obvious, not foolproof.
by Spoom 7y ago
Such an error would be immediately obvious on code review. The idea is to make it obvious, not foolproof.
- mlthoughts2018 7y agoIn static typing paradigms, the idea most certainly is to make it foolproof and not merely easy to spot. Literally to convert the problem into something the compiler can prove is unbroken. Not saying this makes static typing better or anything, just pointing out that “easy to spot in code review” is massively different from “absolute mathematical proof this problem isn’t affecting me.” I’d argue you rarely care about such compiler proofs in real software development, but that’s beside the point if you assume a static typing paradigm has already been chosen.