I needed to Google about "bump allocators". I found this: https://stackoverflow.com/questions/62076569/is-this-implementation-of-malloc-a-bump-allocator https:

I needed to Google about "bump allocators". I found this: https://stackoverflow.com/questions/62076569/is-this-implementation-of-malloc-a-bump-allocator https://stackoverflow.com/questions/62076569/is-this-impleme... > It's a really naive allocator that can be very fast due to the tiny amount of housekeeping involved, but you have to live with a pretty heavy constraint: there's no "free" operation for individual request - you just destroy the whole thing. To me, this sounds like an arena allocator. I remember seeing them in Apache SVN source code a squillion years ago. What's the big deal? For RAII, we can just do placement new in the ctor, and "arena free/delete" in dtor -- which might do nothing in practice. Also, was the original article focused on gamedev? I don't see any mention of it. For us normie programmers working on CRUD apps, we don't need bump/arena allocators. Ctor->new, RAII/Dtor->delete is just fine for us.