16 Jan
2014
16 Jan
'14
9:04 p.m.
2014/1/16 Nat Goodspeed <nat@lindenlab.com>
Not a bug, I believe. Oliver has clarified in previous mail that when you yield(), the calling fiber isn't waiting *for* anything: it's merely giving the scheduler a chance to run something else. The calling fiber is still ready to run, and can be resumed as soon as the scheduler picks it.
correct - it's a better explanation