[Issue 16106] Calling a fiber from itself causes hard-to-debug stack corruption

via Digitalmars-d-bugs digitalmars-d-bugs at puremagic.com
Tue May 31 08:04:36 PDT 2016


--- Comment #1 from Don <clugdbug at yahoo.com.au> ---
To clarify: I'm asking for the situation where you call a fiber which is not in
state HOLD, to be detected even when compiled without contracts.

I'm not asking for fiber.call() to ever be a no-op.

Ie, fiber.call() should either switch to a different fiber, or else it should
halt execution. It should never cause stack corruption.


More information about the Digitalmars-d-bugs mailing list