This site is being rebuilt and some pages are out of date. For current details, write to [email protected]. This notice goes away when the rebuild is done.

No analytics unless you allow it, no tracking. This site keeps in your browser the language you pick, the theme, its colour, which site you chose, the currency on the pricing page and that you closed this notice; signing in adds session cookies. The legal page has the details.

Sign in

Radar · Rust · Archive · Week 16 · Apr 13 – 19, 2026

build-std: always

Worth knowingtooling

What changed
A new Cargo configuration option, build-std = "always|never", was added to unconditionally rebuild standard library dependencies. The set of standard library dependencies can optionally be customised with a new build-std-crates option.
Production impact
The source does not say.
Try it
Add build-std = "always" to a Cargo.toml and run cargo build.
Source
github.com/rust-lang/rfcs/pull/3874

Understand it, then run it

Run it now

Todayrust
// This program demonstrates the effect of `build-std = "always"`.
// Since Cargo rebuilds the standard library each time, the build
// will take longer than usual.  The program itself is trivial.
fn main() {
    println!("Hello, world!");
}

What it printed when we ran it on Rust 1.98.1 (edition 2024)

Hello, world!

Run sends this program (for Solidity, the contract and its tests) to our own sandbox, where it is compiled and run once, with no network, and what it printed or the test report comes back here. Nothing is kept. Runs are counted per visitor for the day so everyone gets a turn; the details are on the legal page.

Written by gpt-oss-20b from the linked source · claims checked against the sources · archive, not individually reviewed