How furkankirat/arena-allocator works
This is a small header-only C++20 arena allocator, not a multi-service application. Its principal workflow is that a game or other client creates an arena, allocates aligned raw memory or typed objects, then reclaims temporary allocations by resetting the arena or rewinding to a marker. The header also provides array allocation, usage metrics, and move-only ownership of the backing block. The graph reflects the single sampled runtime header; usage examples and other capabilities are documented in the README.
Main entry points: arena_allocator.h Arena allocator
Components 9
Other components
- Game/client
- Arena allocator
include/arena_allocator.h - Backing memory
include/arena_allocator.h - Aligned allocation
include/arena_allocator.h - Typed construction
include/arena_allocator.h - Array allocation
include/arena_allocator.h - Arena reset
include/arena_allocator.h - Marker rewind
include/arena_allocator.h - Usage metrics
include/arena_allocator.h
Connections 13
- Game/client → Arena allocator: creates and uses
README.md - Arena allocator → Backing memory: owns and releases
include/arena_allocator.h - Arena allocator → Aligned allocation: exposes
include/arena_allocator.h - Typed construction → Aligned allocation: allocates via
include/arena_allocator.h - Array allocation → Aligned allocation: allocates via
include/arena_allocator.h - Game/client → Typed construction: requests objects
README.md - Game/client → Array allocation: requests arrays
README.md - Game/client → Arena reset: reclaims allocations
README.md - Game/client → Marker rewind: saves and rewinds
README.md - Game/client → Usage metrics: queries usage
README.md - Arena reset → Arena allocator: rewinds offset
include/arena_allocator.h - Marker rewind → Arena allocator: reads or sets offset
include/arena_allocator.h - Usage metrics → Arena allocator: reads size and offset
include/arena_allocator.h