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 51 · Dec 15 – 21, 2025

Rustup 1.29.0 beta: Call for Testing!

Worth knowingtooling

What changed
The Rust team released a beta version of rustup 1.29.0 and invited the community to test it.
Production impact
The source does not say.
Try it
Install rustup 1.29.0 beta and run rustup update.
Source
blog.rust-lang.org/inside-rust/2025/12/20/rustup-1.29.0-beta-cft/

Understand it, then run it

Run it now

Todayrust
// This program demonstrates that Rust 1.98.1 (edition 2024) can spawn
// multiple threads that run concurrently.  It does not actually download
// anything, but it shows the idea behind rustup's concurrent download
// feature by printing messages from several threads at the same time.
use std::thread;
use std::time::Duration;

fn main() {
    // Spawn three threads that simulate downloading different components.
    let handles: Vec<_> = (1..=3)
        .map(|i| {
            thread::spawn(move || {
                // Simulate a download taking a random amount of time.
                let sleep_time = Duration::from_millis(500 * i);
                thread::sleep(sleep_time);
                println!("Component {} downloaded in {:?} ms", i, sleep_time.as_millis());
            })
        })
        .collect();

    // Wait for all threads to finish.
    for h in handles {
        h.join().unwrap();
    }

    println!("All components downloaded concurrently.");
}

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

Component 1 downloaded in 500 ms
Component 2 downloaded in 1000 ms
Component 3 downloaded in 1500 ms
All components downloaded concurrently.

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