6 Feb
2009
6 Feb
'09
9:15 a.m.
Greg Ewing writes:
The fact that yielding is going on is not of interest in that situation -- it's just an implementation detail. What you really want to express is calling another function, but without losing your status of coroutine-ness.
But doesn't "yield" in the sense of "yield the right of way" mean exactly that? Or am I not understanding what you mean by retain status as a coreoutine? I don't know if this is an argument for or against using "yield" in this context.