Radar · Rust · Archive · Week 14 · Mar 30 – Apr 5, 2026

Fix typo in 3654-return-type-notation.md

Nice to knowtooling

What changed: Several typos were corrected in the return‑type‑notation RFC.
Production impact: The source does not say.
Try it: View the rendered RFC to see the corrected wording.
Source: github.com/rust-lang/rfcs/pull/3939

Understand it, then run it

The change fixes a few spelling mistakes in the RFC that explains how to write return‑type notation. The RFC is a document that describes a language feature; it does not contain executable code. Because the change only corrects words, nothing in the Rust compiler or standard library is affected. If you read the RFC, you will now see the words immediate, explorations, and functionality spelled correctly.

Run it now

Todayrust

// This program demonstrates that the Rust compiler is unaffected by the typo fix.
// It simply prints a message confirming that the language features remain the same.

fn main() {
    println!("Rust compiler unchanged; typo fix only affects documentation.");
}

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

Rust compiler unchanged; typo fix only affects documentation.

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