I mentioned it in the next section: > The standard library includes a set of allocators which don't reuse allocations, preventing use-after-free, and which cat

I mentioned it in the next section: > The standard library includes a set of allocators which don't reuse allocations, preventing use-after-free, and which catch double-free. I'm not clear yet on how high the runtime and memory overhead are though, which will dictate when it is practical to use these. I didn't include it in the table because I'm not yet convinced that the overhead will be low enough that people will actually ship software using those allocators. (All the zig programs I've written so far use the libc allocator and are definitely susceptible to UAF) Perhaps I'll spend some time measuring it this week and post an update.