Literally the definition of the integers is that (x + 1) != x. Wrapping is bad enough, but at least tends to makes failures noticeable. Saturating arithmetic makes it really hard to see that a failure has occurred.<p>Depending on the performance penalty you&#x27;re willing to take, there&#x27;s good alternatives to wrapping, such as: A) 64-bit integers, B) bigints, C) crashing on overflow.<p>Sure, saturation might be useful in certain circumstances, like manipulating audio samples, but it&#x27;s generally something you want to make explicit. Using it everywhere? It&#x27;s madness!