upvote
Generational moving GCs work much like arenas, and they work without the limitations of arenas and without the performance hit of malloc/free. That's not to say arenas aren't very efficient and useful, but few languages make them convenient and composable enough (Zig), and even then they need to be used with care.
reply
> and without the performance hit of malloc/free.

Arenas avoid most of the performance problems of malloc/free.

I think the bigger problem with arenas and manual management is memory lifetime is very hard to get right, particularly in the context of concurrent operations. It also cuts away algorithms you can do.

reply
> Arenas avoid most of the performance problems of malloc/free.

Sure, but they're not fully general, which is why you also need malloc/free for things that don't work well in arenas (or write the equivalent of malloc/free on top of arenas, which is what you need to do in Goose: https://github.com/aardappel/goose/blob/master/bench/kostya/...).

Also, arenas can be an even better fit for languages with good GCs than languages without a GC.

reply
[dead]
reply