core.thread.Fiber --- runtime stack overflow unlike goroutines

[Kagamin via Digitalmars-d-learn]

On Thursday, 14 August 2014 at 18:52:00 UTC, Sean Kelly wrote:
> On 64 bit, reserve a huge chunk of memory, set a SEGV handler 
> and commit more as needed. Basically how kernel thread stacks 
> work. I've been meaning to do this but haven't gotten around to 
> it yet.

AFAIK, OS already provides this transparently: when you allocate 
memory, OS only reserves the memory range and commits pages when 
they are accessed.