On 01.04.2015, at 20:51, Eliot Miranda <eliot.miranda@gmail.com> wrote:
Ah, I misread what you were proposing before. Simpler is better for understanding :)
Assuming there are more runnable processes at the active priority, could there be a scenario where the #jump context is resumed after the yield, before the forked process had a chance to run? Or would we have to fork it at a higher priority? Could either in any way mess with the order of process activation, which would not happen with the current #jump implementation?