Code for Game Developers - Anatomy of a Memory Allocation

…For example: * bump allocator * bump allocator with expandable memory (aka arena allocator) * testing allocator (very useful when you are writing tests because it will scream at you when your code has memory leaks) Maybe write some tests that allocate some memory to see how to use them. And of course watch this excellent talk by Benjamin Feng: [video This talk about memory allocation by Jorge Rodriguez is also great: [video Also, you'll need to understand the different types of **pointers** in Zig, so have a look at Solving Common Pointer Conundrums by Loris Cro: [video As for some materials on stack, heap, etc, try googling something like "memory layout of a C program". I woul…

Think about these questions: 1. how much memory to allocate? 2. when to allocate it? 3. what to do when memory allocation fails? The answers to these questions are platform and architecture specific, and since one of the design goal of zig is to be compilable for any architecture, it cannot answer these questions for you. It's up to you to define an allocation strategy (i.e. answer to the questions above). Zig defines an interface that you can implement to allocate/deallocate memory. And in order to cover common use cases, Zig also provides several implementations of that interface. But since Zig exposes such interface to you, you always have the option to allocate/deallocate memory howev…