Skip to content- Sources: primary, discussion
- Summary: FORGE Lab reports soundness bugs in std and core, including a panic safety bug in MapWindows::clone, a str::replace fast path that could produce non-UTF-8 Strings from a custom Pattern, process::exit unmapping the main thread's signal stack, and CommandExt::exec writing environ under a read lock. Two of its reports remain open. Rust 1.100, due on 2026-11-12, stabilizes the Allocator API with a rule that implementors must never unwind, after unwinding allocators proved a pervasive source of unsoundness.
- Why it matters: Code that implements Allocator, Pattern or other traits consumed by unsafe std code should expect stricter contracts, and teams writing unsafe Rust get concrete patterns to audit.
- Background: A safe Rust API is sound when no safe caller can trigger undefined behavior, so the unsafe code beneath it must defend against panics, inconsistent trait implementations and OS state. The authors built Rudra, a 2021 static analyzer for such bugs, and say AI agents now make the OS boundary practical to search.
- Follow-up: Rust 1.100 release on 2026-11-12 with the Allocator API.