miniblog.

← Back to all posts
Feb 13, 2022 at 19:55
My Rust rule of thumb: if there are no lifetimes in your return type, you probably don't need to specify the lifetimes in your arguments. (I know clippy will point out simple cases of unnecessary lifetimes, but plenty other cases occur IME.)

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?