That's actually better than the situation in C. In C, debug `malloc` may very well behave the same run after run. Then you move into production, and release `

That's actually better than the situation in C. In C, debug `malloc` may very well behave the same run after run. Then you move into production, and release `malloc` behaves differently to debug `malloc`. Suddenly a latent bug that was there all along shows itself in release, but fails to reproduce in debug. With the randomized behavior you describe in golang, the bug probably will show in debug and be caught.