> > This also seems like a very bad idea: there is no reason for the language hide concurrency behind an INI or even worse a compilation flag. >
This is not because someone wants it that way. This situation is solely due to the fact that the Scheduler contradicts of Fiber. - The Scheduler expects to switch contexts as it sees fit. - Fiber expects context switching to occur only between the Fiber-parent and its child. Of course, the switching mechanism can be modified, and the logic of the main context can also be changed. The problem is that, at a logical level, these two approaches are mutually exclusive. For example, the Swow project introduced a separate coroutine library (libcat) and abandoned Fiber. But we cannot do the same. --- Ed.
