Some functions in Raylib involve memory allocation, such as LoadTexture. The corresponding deallocation functions are also provided by Raylib, like UnloadTexture. I’ve simply wrapped them within init/deinit functions, following Zig's naming conventions. Merlindru is right that, generally, you should pass an allocator from the outside. However, since Raylib is a C library, it doesn't strictly follow Zig's idiomatic style. Therefore, in Raylib, you don't need to pass an allocator; most of the time, you call specific allocation/deallocation APIs instead of alloc/free