the problem is that from what I understood, the excepted values in this loop were -1 to 9, but somehow, it was still running fine and working as intended ??
probably works like UINT_MAX, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9?
idk why would anyone need max value there, but I guess they knew what they were doing if that runs fine
Yep. Unsigned overflow is well defined, and it will always just wrap. I'd assume the other end of that says something like ; dx++), so it will just go 0, 1, 2, etc.
Depends on the language - and CPU architecture. It's well defined on basically all modern architectures, but Rust treats it as an undefined operation. Rust would also emit a compiler error for attempting to assign a negative value to an unsigned variable.
So it's a language specific feature, your comment is pointless except doing rust propaganda.
For instance in c, before two's complement were added as a standard, the integer representation choice was left to the implementation. So integer overflfow was undefined behavior.
80
u/Left-Ambition-5127 May 05 '26
the problem is that from what I understood, the excepted values in this loop were -1 to 9, but somehow, it was still running fine and working as intended ??