Well you couldn't you just use a different one in that case? The variable would just be like a suggestion.

Most programmers don't prefer thread local mutable state over a single pointer argument. Especially for general purpose code (i.e., not specific to a single purpose/project). With the mutable state version, you have to clearly define which state you're using and when (which named allocator/arena variable), and if you're mutating it in place and then restoring it, there can be some pretty obvious issues.

Given this thread is completely off the rails from anything specific to allocators or arenas, and even Zig, I will now exit.