|
|
|
|
|
|
by DagAgren
2246 days ago
|
|
|
It's not, that is a perfectly logical thing to do: Use a more generic primitive to implement more specific functionality. It's not about liking one thing or another more. It's that coroutines are coroutines, and cooperative multitasking is cooperative multitasking. The two are often confused, and all I am saying is that that is incorrect. Cooperative multitasking can easily be implemented with coroutines, but doesn't have to be. You could implement coroutines with cooperative multitasking but doing so is highly silly and a massive hack. |
|
|
And both are equally capable is all I'm saying.
Well, I suppose we've come close enough then to move on.