Here's a typo that had dramatic effects:
if(processed_count =! container.size())
. . .
Result: the code always thought that the whole container had been processed, even when it wasn't.
Had the codebase been running at maximum warnings, and treating warnings as errors, this would never have happened. Those compilation conditions are now active.
Always compile at maximum warnings and treat warnings as errors.
Post a Comment