As far as I know, it's common practice to place
statements of this sort where the code path should be
assert 0, 'This should not happen.'
This helps catch logic errors if something is changed
This currently triggers the constCond check. I'd like to
see an option to ignore assertions with a constant of
zero (or False). Assertions with a constant of 1 are
almost certainly an error, on the other hand.
Log in to post a comment.