> If 16 bits is enough, use an explicitly 16-bit integer.
This will often generate more code. So don't do this except when it saves a modest amount of memory.
This will often generate more code. So don't do this except when it saves a modest amount of memory.
In most places, if you're using an `int` for non-address-y stuff you're just wasting space on wider archs, or you're overflowing on less wide ones. The only exception off the top of my head is "I have an array of bytes, but want to bulk process more efficiently than u8 would allow". Things like `size_t` (or explicit SIMD types!) are still probably a better choice there, if only to simplify the rule to "just don't use int".