Radar · Rust · Archive · Week 3 · Jan 13 – 19, 2025
Return‑Type‑Notation RFC – Typo Fix
Nice to knowlanguage
- What changed
- A typo in the return‑type‑notation RFC was corrected.
- Production impact
- The source does not say.
- Try it
- Read the RFC to see the corrected wording.
- Source
- github.com/rust-lang/rfcs/pull/3763
Understand it, then run it
The Return‑Type‑Notation RFC had a small typo that was corrected. The RFC explains how function signatures look, especially the part after the arrow ->. The typo was only in the documentation, not in the compiler or standard library. So nothing in your code changes, but the text you read about return types is now accurate.
Run it now
// This program demonstrates that the compiler and standard library are unchanged
// by the typo fix in the Return‑Type‑Notation RFC. It simply prints a message.
fn main() {
println!("Return‑Type‑Notation RFC typo fixed; no code impact.");
}
What it printed when we ran it on Rust 1.98.1 (edition 2024)
Return‑Type‑Notation RFC typo fixed; no code impact.
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