Iddqd, or the hardest kind of unsafe Rust
hasheddan
24 points
4 comments
June 02, 2026
Related Discussions
Found 5 related stories in 93.9ms across 9,294 title embeddings via pgvector HNSW
- An incoherent Rust emschwartz · 160 pts · March 23, 2026 · 59% similar
- Bun's unreleased Rust port has 13,365 unsafe blocks helloplanets · 51 pts · May 22, 2026 · 56% similar
- Noq: n0's new QUIC implementation in Rust od0 · 179 pts · March 19, 2026 · 56% similar
- Bugs Rust won't catch lwhsiao · 108 pts · April 29, 2026 · 54% similar
- Lunacy: A Lua JIT Written in Rust fanf2 · 16 pts · May 30, 2026 · 53% similar
Discussion Highlights (1 comments)
alilleybrinker
The section on how to do software assurance of unsafe code in Rust is excellent. A lot of prior guidance I've seen tends to stop at the level of running Miri, but (as the article says) there are things Miri won't catch. The model-based tests with a known-good oracle and the use of fault injection (especially panic-related behavior) are really good. Safety in the face of panics in Rust can be hard to reason about, and the standard library itself has made errors with those semantics in the past. Great work Rain and Oxide for building something so useful and assuring it so robustly!