miniblog.

← Back to all posts
Dec 4, 2019 at 07:15
An unsoundness in Rust using only safe code! Rust provides a bunch of guarantees so it's always interesting to see the rare ways it can be broken. I think this is the first unsoundness since the thread spawn issue after 1.0? https://internals.rust-lang.org/t/unsoundness-in-pin/11311

Related Posts

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?
Apr 3, 2026 at 00:37
21
Rust and RISC-V both feel like they've reached critical mass and I'd guess that they'll be used more in 5 years than they are today. What other technologies fit this description?