> and putting it on the stack turns out to be cheaper than heap allocating it. Well, more so that C has no concept of the heap. That's entirely contained withi

> and putting it on the stack turns out to be cheaper than heap allocating it. Well, more so that C has no concept of the heap. That's entirely contained within the C libraries. So, the language implementation itself can't do heap allocations (at least, not without sacrificing any chance of using it in embedded or kernel dev situations where you don't have heap allocation, or where you need to use custom allocators)