This whole post is a strawman. I never said my reason was being tight on resources. Please reread the thread. Also don't forget that on modern architectures, the stack and heap can't "collide", because of guard pages.

> what are you going to do with the rest of the stack?

I'll leave it for the rest of the system. My app will use less memory, and since memory locality is improved, there will be fewer cache misses, meaning it runs faster too.

> let's say you take a function call that is about to overflow the stack

Stack overflows are impossible thanks to the comptime upper_bound parameter. That's the entire premise of this thread.