"The results are undefined. That means the compiler is free to do anything, like emailing your boss about this transgression."
miniblog.
Related Posts
8
Co-Authored-By: An old Stack Overflow answer, blindly accepting the compiler's suggestions, and a linter.
2
I would have thought that invoking a C compiler would be a solved problem. Looking at Rust's cc crate there's a remarkable long tail of corner cases to fix.
Exotic CPUs, microarchitectures, compiler differences, operating system differences, etc.
Today I learnt that `cargo fix` won't fix code with compiler errors by default, but you can override this!
$ cargo fix --broken-code --allow-dirty && cargo clippy --fix --allow-dirty
This incantation does exactly what I wanted :)