Why Rust's Explicit Integer Types Are Better Than C's Default Int
Thoughts on Integers (2023)
I explore how popular languages like C, Go, and Swift bias developers toward using generic signed integers, often leading to subtle bugs. In contrast, Rust forces explicit type choices, preventing negative array indexes and clarifying overflow behavior. While C treats signed overflow as undefined behavior for performance, I argue that Rust's approach offers a safer, more intuitive model for modern systems programming.
If you have an integer which you want to treat arithmetically as opposed to in some modular space, Make. It. Signed. If you need more bits, get more bits. Keep it signed.