miniblog.

← Back to all posts
Apr 9, 2016 at 18:42
Even in 2016, we're still exploring the best way to display CLI compiler errors. Some interesting iterations in Rust
Overhaul borrowck error messages and compiler error formatting generally by nikomatsakis · Pull Request #32756 · rust-lang/rust
Overhaul borrowck error messages and compiler error formatting generally by nikomatsakis · Pull Request #32756 · rust-lang/rust
This is a major overhaul of how the compiler reports errors. The primary goal is to be able to give many spans within the same overall context, such as this: ./borrow-errors.rs:73:17: 73:20: error:...

Related Posts

Feb 3, 2026 at 10:17
61
Date of birth pickers are a surprisingly nuanced UI problem. What do you pick as the initial value? How do you allow users to easily move by large amounts (years) as well as small amounts (the exact day)? Defaulting to today and even allowing future dates is funny though.
Photo
Jan 22, 2026 at 20:11
10
The vast majority of libraries have a single maintainer. Even if you weight by downloads, roughly half of downloaded libraries have a single maintainer too.
Open Source is one person
Open Source is one person
The Register recently published a story titled Putin on the code: DoD reportedly relies on utility written by Russian dev. They should be ashamed of this story. This poor open source developer is getting beat up now to score some internet points. It’s very upsetting. But anyway, let’s look at some receipts. If you’re not real smrt, it seems like pointing out an open source project is written by one person in a country you don’t like is a bad thing. It could be. But it also could be the software running THE WHOLE F*CKING PLANET is written by one person. In a country. But we have no idea which country. It’s not the same person mind you, but it’s one person.
Dec 14, 2025 at 00:35
14
One subtle behaviour of Claude that wasn't obvious to me: whilst each conversation is transient, permissions persist across conversations. So if you've given permission to run e.g. 'cargo test' or even 'cargo run', you need to be sure that all future invocations are safe too. You can see the current permissions with /permissions.