<@U4S7P1QSJ> Conceptually, it is the same. Just a ...
# coroutinese
elizarov
10/10/2017, 1:44 PM@rrva Conceptually, it is the same. Just a different name for the same concept. https://en.wikipedia.org/wiki/Fiber_(computer_science)
r
rrva
10/10/2017, 2:01 PMThis does not apply then when comparing the kotlin flavor to quasar? http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4024.pdf
rrva
10/10/2017, 2:01 PMit’s how c++/boost defined fibers I guess
rrva
10/10/2017, 2:01 PMIn short - the difference between coroutines and fibers is, that the context switch between fibers is managed by a scheduler (selects the next fiber ...). Coroutines don’t have a concept of a scheduler.
rrva
10/10/2017, 2:01 PMe
elizarov
10/10/2017, 2:12 PMIt is the same. The difference some people put into Fibers vs Coroutines are immaginary and is invented by those people who think they are different. E.g., it might be one immaginary difference in C++ and a completely other difference somewhere else. In fact, it is the same concept.
elizarov
10/10/2017, 2:20 PMThe fact that one async programming proposal in C++ is called “fibers” and the other is called “coroutines” is a pure chance. They could have been called the other way around without truly changing anything.
4 Views