The guarantee Rust makes is conditional: write no unsafe, and no amount of bad code can produce a memory-safety bug.

Added to korrents 20 May 2026 · How quotes work · Something wrong? Tell us

Related korrents

Our reading — they may agree, disagree or merely touch the same thing. Closest first: a shared subject counts for most, then how near the wording is.

• Rust's defining experience is that once the code compiles it works — not literally true, but true often enough that people keep saying it. ARAlice Ryhl20 May 2026similar wording
• Memory safety means an entire class of bug is impossible no matter how bad the code is — and it is the class that becomes security vulnerabilities. ARAlice Ryhl20 May 2026similar wording
• The case for Rust is stronger against C++ than against JavaScript, because in C++ an ordinary mistake is usually a security vulnerability. ARAlice Ryhl20 May 2026similar wording
• A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting. ARAlice Ryhl20 May 2026similar wording
• Application code should contain no unsafe at all: unsafe is how you add a missing feature to the language, not how you write a server. ARAlice Ryhl20 May 2026similar wording

See this on the map →