miniblog.

← Back to all posts
Oct 12, 2015 at 21:18
Rust is the only language I know that systematically tests new compilers against a big real-world corpus: https://internals.rust-lang.org/t/regression-reports-stable-2015-09-17-vs-beta-2015-10-02-nightly-10-06/2737 amazing!
Regression reports stable-2015-09-17 vs. beta-2015-10-02/nightly-10-06
Regression reports stable-2015-09-17 vs. beta-2015-10-02/nightly-10-06
stable-2015-09-17 vs. beta-2015-10-02 stable-2015-09-17 vs. nightly-2015-10-06 Lot’s of reported regressions. I haven’t looked at them yet.

Related Posts

Jul 9, 2026 at 19:44
1
It's really satisfying fixing crashes in rust-analyzer. You can start from a panic message and dig until you've got a tiny Rust program that triggers the problem. (It's usually an issue with incomplete source files breaking invariants.)
fix: Crash on code actions when an unresolved module is present · rust-lang/rust-analyzer@9d343e9
fix: Crash on code actions when an unresolved module is present · rust-lang/rust-analyzer@9d343e9
Previously rust-analyzer assumed that a module always had an item list, which isn't true for unresolved modules. Handle this situation gracefully instead of panicking, and add a test. AI disc...
Jun 5, 2026 at 08:53
31
Today I learnt about clippy::clone_on_ref_ptr, which complains about t.clone() on a Rc<Thing>. You write Rc::clone(t) instead, so it's obvious it's a cheap clone. It's a nice approach, because it makes the expensive clones more obvious.
Clippy Lints
A collection of lints to catch common mistakes and improve your Rust code.
May 1, 2026 at 18:58
214
It's funny how languages can offer multiple forms of syntax, but formatters standardise to a single form. E.g. single vs double quotes in JS, optional semicolons in JS, different ways of grouping imports in Rust. Should new languages be more syntactically opinionated?