Lightning Talk: Rust Without ‘Unsafe’ Is as Unsafe as C++
summary
Shows a concrete example that produces a dangling reference in safe Rust by using ordinary borrow/bind syntax plus a small macro that hides temporaries so a reference is bound to an object that is dropped at scope end. The code prints garbage rather than crashing, demonstrating a reproducible safety hole without writing any unsafe code. The issue traces back to 2015 and remains unresolved, so the demo actually compiles and runs and exposes a borrow checker bypass in current Rust.
AI-written summary · about
related talks
54mMemory Safety with Rust
44mUnsafe Rust
35mLet’s Talk About Rust
28m"Rust Interop: Memory Safety Across Foreign Function Boundaries"
01h 05mKeynote - Rust: confident, productive systems programming
01h 14mRust: A Friendly Introduction
45mBuilding Safe and Secure Systems in Rust
19mCounterexamples in Safe Rust