That confused me for a second too, but I think that’s the point. I assume the idea (that I’m not totally sold on) is that you will hardly ever have a long-running enough debug build process for it to be an actual issue more often than you will really need to reuse memory while debugging code. This is in exchange for being “absolutely certain” that your program did not have any UAFs, double frees, OOB, etc. if you’re using it like intended. I think it’s a weird default but a sensible design in and of itself.
That confused me for a second too, but I think that’s the point. I assume the idea (that I’m not totally sold on) is that you will hardly ever have a long-running enough debug build process for it to be an actual issue more often than you will really need to reuse memory while debugging code. This is in exchange for being “absolutely certain” that your program did not have any UAFs, double frees, OOB, etc. if you’re using it like intended. I think it’s a weird default but a sensible design in and of itself.
score 1 · canonical
I’ll need to dig into which allocator is used for the gpa handed to init for ReleaseSafe builds then…
score 1 · canonical