
The unsafe Keyword

Why Rust is different, with Alice Ryhl
Topic 6 of 13
Published May 20, 2026 · Clip 26:56–31:20 (4:24)
The guest explains unsafe as the escape hatch: without unsafe, certain bug classes (security vulnerabilities) cannot occur; unsafe operations have rules, and violating them can reintroduce those bugs. Unsafe doesn't disable the borrow checker; it just enables unsafe-marked functions like get_unchecked. Sensible uses are rare in backend servers; mostly unsafe is used to build new language features (e.g., implementing a vector with private fields and a safe API) or to call into C libraries with safe wrappers.