The infinite loop on unsigned integers exemplifies a failure in C&#x27;s type system: integer wraparound is so rarely desirable behavior that a range error on wraparound would prevent many such errors from failing silently.<p>There&#x27;s an argument to be made that this check would hurt performance (and I buy that argument--given C&#x27;s goals and the time when it was made, the type system compromises it made make sense). But it would be nice if processor manufacturers made add&#x2F;sub instructions that detected wraparound, which would allow languages to implement such checks performantly.