miniblog.

← Back to all posts
May 16, 2015 at 16:22
Proposed an improvement to errors in the rust compiler, and a patch landed in less than a day. Seriously impressed.
Suggestion: Syntax errors for malformed `extern` statements could be clearer · Issue #25468 · rust-lang/rust
Suggestion: Syntax errors for malformed `extern` statements could be clearer · Issue #25468 · rust-lang/rust
This is a very minor bit of polish, but I bumped into it. Given the following syntactically invalid code: extern crte hyper; fn main() { println!("hello world") } rustc produces the error: $ rustc ...

Related Posts

Dec 14, 2025 at 21:45
8
Co-Authored-By: An old Stack Overflow answer, blindly accepting the compiler's suggestions, and a linter.
Oct 5, 2025 at 20:23
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.
cc-rs/CHANGELOG.md at main · rust-lang/cc-rs
cc-rs/CHANGELOG.md at main · rust-lang/cc-rs
Rust library for build scripts to compile C/C++ code into a Rust library - rust-lang/cc-rs
Jan 15, 2025 at 08:19
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 :)