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 8 · Feb 17 – 23, 2025

RFC: project goals for 2025 H1

Worth knowingtooling

What changed
The Rust team merged a proposal that lists 40 project goals for 2025 H1, including three flagship goals: improving async ergonomics, stabilizing compiler options for low‑level projects, and preparing for async and sync generators.
Production impact
The source does not say.
Try it
Read the proposal to see which goals might affect your build pipeline.
Source
github.com/rust-lang/rfcs/pull/3764

Understand it, then run it

The Rust team announced a list of 40 goals for the first half of 2025. Three of those goals are highlighted: making asynchronous Rust easier to use, stabilizing compiler options for low‑level projects, and adding support for asynchronous and synchronous generators. The announcement is a planning document; it does not change any language feature that you can use right now.

Run it now

Todayrust
// This program simply prints the goals announced in the RFC.
// It demonstrates that the change is a planning document, not a language feature.
fn main() {
    println!("Rust 2025H1 project goals:");
    println!("1. Improve async ergonomics");
    println!("2. Stabilize compiler options for low‑level projects");
    println!("3. Add support for async and sync generators");
}

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

Rust 2025H1 project goals:
1. Improve async ergonomics
2. Stabilize compiler options for low‑level projects
3. Add support for async and sync generators

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