I don't think we want the Windows fibers change - if an app specifically calls co_derive() rather than co_create(), it's because it explicitly wants to manage the stack itself - perhaps to snapshot and restore the stack, or maybe walk it for garbage-collection purposes. Secretly storing the stack elsewhere would just break things, so it's better for co_derive() to just return 0, and then the app can make an informed decision about what it wants to do.
I don't think we want the Windows fibers change - if an app specifically calls
co_derive()
rather thanco_create()
, it's because it explicitly wants to manage the stack itself - perhaps to snapshot and restore the stack, or maybe walk it for garbage-collection purposes. Secretly storing the stack elsewhere would just break things, so it's better forco_derive()
to just return 0, and then the app can make an informed decision about what it wants to do.