Skip to content

Conversation

@jkarneges
Copy link
Member

@jkarneges jkarneges commented Jan 20, 2026

After discussing with some folks about terminology, I think "arena" is not the best term for what we're doing in this module. While "arena" is often used in scenarios where memory is preallocated, which we are doing, it typically refers to the ability/act to do mass freeing of objects within that memory, especially of objects without destructors, and that's not us. We don't do any mass freeing and all of our objects have destructors (drop methods).

Selecting "memorypool" as a new name for the module, in part because it's generic enough give us leeway as to what exactly goes on in the module, and also because Zig uses this name for their built-in slab-like allocator which is very close to what we are actually doing.

@jkarneges jkarneges requested a review from a team January 20, 2026 19:13
@jkarneges jkarneges merged commit d893603 into main Jan 21, 2026
19 checks passed
@jkarneges jkarneges deleted the jkarneges/rename-arena branch January 21, 2026 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants