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

[Sean Kelly via Digitalmars-d-learn]

On Friday, 15 August 2014 at 15:25:23 UTC, Dicebot wrote:
>
> No, I was referring to the proposal to supply bigger stack size 
> to Fiber constructor - AFAIR it currently does allocate that 
> memory eagerly (and does not use any OS CoW tools), doesn't it?

I thought it did, but apparently the behavior of VirtualAlloc and 
mmap (which Fiber uses to allocate the stack) simply reserves the 
range and then commits it lazily, even though what you've told it 
to do is allocate the memory.  This is really great news since it 
means that no code changes will be required to do the thing I 
wanted to do anyway.