🚀 go-pugleaf

But wait a minute, it actually _uses_ 160Mb! In your example compiler
could optimize it away (well, it could optimize away the whole thing)
but consider the following modification:
	caller allocates 80Mb array and writes something there;
	test1 also allocates 80Mb and uses it;
	test1 finishes and deallocate his 80Mb;
	after that the caller continues to use _his_ array.
When the test1 runs it should have 80Mb for its own array _and_ the first
array should be preserved somewhere. After all, caller would be very upset
if his very own array would disappear or would lose its content. So when
the test1 is being executed you need 160Mb total. No matter where you'll
place it, but you can't get out alive without this amount under any system
with any compiler.
								Al