What you describe is antithetical to idiomatic Rust, written by a skilled Rust programmer. To uphold the spirit of Rust, a C program must go through a process

What you describe is antithetical to idiomatic Rust, written by a skilled Rust programmer. To uphold the spirit of Rust, a C program must go through a process where assumptions are laid bare and footguns are dismantled. Applying an automatic process which arbitrarily changes the behavior from the implementation-dependent compilation of a C program just gets you a messy slop of hidden bugs collected inside an opaque, "safe" garbage can. You don't get to Rust's reliability by applying a translation which discards it! > Also, if you go this route, you’d have to do similar gnarly stuff for all arithmetic on integers where you cannot prove there will not be overflow. Damn straight. That's what C is! It was always this bad, as those of us who have struggled to control it can attest. Faithful translation to unsafe Rust just makes it obvious.