Arguably Rust does better for this particular example because, for debug builds and optionally release builds, overflows trigger an error. If you explicitly want wrapping arithmetic in Rust you should use b.wrapping_add(c) in this case, otherwise you'll get a runtime error.

So for instance the following code generates an error (I add to add the function call indirection otherwise rustc would even refuse to compile the straightforward `200u8 + 100u8`):

    fn main() {
        println!("{}", add(200, 100));
    }

    fn add(a: u8, b: u8) -> u8 {
        a + b
    }

    // thread 'main' panicked at 'attempt to add with overflow', test.rs:6:5
    // note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

IMO that's a more robust and generic solution than hoping that `int` promotion will prevent the overflow. The drawback is that it incurs a performance hit and is therefore only enabled in debug builds by default.