For example, the good old `assert` in software. Asserts are to detect impossible states, and hence if an assert trips, the software is in an unknown state, and what it will do next is unpredictable. Therefore, an assert must go directly to jail, not pass Go, and not collect $200.
I get pushback all the time on this,
1. people use assert()'s to validate input
2. people insist that their program can continue operating after an assert trips
3. people insist that their program cannot be allowed to fail, and that they are capable of predicting what their program will do next
I get pushback all the time on this,
1. people use assert()'s to validate input
2. people insist that their program can continue operating after an assert trips
3. people insist that their program cannot be allowed to fail, and that they are capable of predicting what their program will do next