How to speed up the Rust compiler in July 2026
My last post on the Rust compiler’s performance was in December 2025. Let’s see what has happened since then.
Be kind and be useful.
My last post on the Rust compiler’s performance was in December 2025. Let’s see what has happened since then.
It has been more than six months since my last post on the Rust compiler’s performance. In that time I lost one job and gained another. I have less time to work directly on the Rust compiler than I used to, but I am still doing some stuff, while also working on other interesting things.
I am happy to announce that I have joined a new startup called VectorWare. The linked website is currently very bare-boned, but the company aims to use Rust to improve the state of GPU programming.
Did you know that macOS has a secret setting that can make Rust builds faster? It can also make Rust tests faster (sometimes massively so). It probably even has similar effects for other compiled languages such as C, C++, Go, and Swift. It sounds crazy, but read on…
If you are using #[derive(Arbitrary)] to fuzz your Rust code, update the Arbitrary crate to v1.4.2 to get some compile time reductions and possibly some fuzzing speed improvements.
UPDATE 2025-09-03: I have found a new job and will be starting next week. I will post more details soon. Many thanks to everyone who helped publicize this post and to everyone who contacted me about possible work. Rust is being used in many interesting places!
Rust’s proc macros are powerful but tricky, and have some compile-time costs. This post is about a new tool to help quantify and reduce some of those costs.
It has been two months since my last post on the Rust compiler’s performance. Time for a small update.
My house is now free from the direct burning of fossil fuels. Here’s how I did it.
It has been just over a year since my last update on the Rust compiler’s performance. Let’s get into it. The information about metrics at the top of this post still applies.