Allow swallow in checkAllAllocationFailures?

Brainstorming
,
1

There is a very useful thing checkAllAllocationFailures.

but it has a limitation:
If my code ignores OOM and doesn’t proxy it up, it gives an error that OOM is swallowed.

Apparently it is very easy to face such a case: _ = arena.reset.

So I did a custom checkAllAllocationFailures that allows swallowing specifically for one function testing.
It feels bad and rather smell/low quality fix.

how would you handle it?

2

You would ideally surface OOM all the way to the place where you handle OOMs. If you have code that tries to free memory, after which it retries before giving up, that would be where you would surface it. For most Zig code (that I have written and seen written), this would be the main entry point, and handling it constitutes exiting with an error :laughing: