miniblog.

← Back to all posts
Oct 2, 2016 at 04:20
Rust 1.12 now supports coercing values of type T to type Option<T>! https://github.com/rust-lang/rust/pull/34828 Introduces some interesting API possibilities.
core: impl From<T> for Option<T> by seanmonstar · Pull Request #34828 · rust-lang/rust
core: impl From<T> for Option<T> by seanmonstar · Pull Request #34828 · rust-lang/rust
First, the semantics of this impl seem spot on. If I have a value T, and I wish to make a Option&lt;T&gt;, then Option::from(val) should always give Some(val). Second, this allows improvement for s...

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?