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 9 · Feb 23 – Mar 1, 2026

Rust debugging survey 2026

Worth knowingtooling

What changed
The Rust team released a survey to gather feedback on debugging practices.
Production impact
The source does not say.
Try it
Take the survey to share your debugging experience.
Source
blog.rust-lang.org/2026/02/23/rust-debugging-survey-2026/

Understand it, then run it

The Rust team has published a new survey about debugging. The survey asks developers what difficulties they face when debugging Rust code. It is meant to help the team understand where the current debugging tools fall short. The survey will close on March 13, 2026, and the results will be shared on the Rust blog.

Run it now

Todayrust
// This program simply prints a reminder to fill out the Rust debugging survey.
// The survey is not yet integrated into the compiler, so we just show a message.
fn main() {
    println!("Rust debugging survey 2026 is open until March 13, 2026.");
}

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

Rust debugging survey 2026 is open until March 13, 2026.

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