PRACTICAL MEMORY SAFETY

Summary from the TLDR InfoSec newsletter

Memory safety is most practically defined as having intuitive and easily followed rules unless explicitly marked with a warning sign. Systems like Fil-C offer a spectrum of safety through runtime checks, but they still allow unmarked memory overwrites within an allocation, leaving unchecked "memory footguns" for developers to navigate. Ultimately, genuine memory safety relieves developers from worrying about abstract machine rules so they can focus on their actual work.