Nicw talk. This talk is about c++ coroutine on the compiler-level. Audiance may need some knowledge about how to use coroutine and some basic concept about c++ coroutine first.
Lazy evaluation. Cool trick. Until now i was calling this concept generators, like we have in python. Not used much in python world. Generator should be asymetric coroutine limited to one function body. This is same as javascript async&await - also not called coroutines. Highly recomend trying out Lua coroutines, which are symetric(allows to switch to any other coro not only yield to caller), also not limited to single function body. I got spoiled by Lua coroutines and it really bothers me now when someone mistakes simple generators for coroutines. With coroutines + simple scheduler you can have cooperative threading thingy with all positive threading stuff and none of negative stuff - no mutexes. Just finding out a lot of conflict in c++ coroutine discussions. Feels like if current c++20 coroutine was just renamed to generators everyone would get along.
![fellow fellow - PROUD feat. INK WARUNTORN [STRING QUARTET]](http://i.ytimg.com/vi/BQrVkMPTdHE/mqdefault.jpg)
thx a lot for this presentation, cool explanation of coroutines.
Amazing video. Thanks for sharing.
Nicw talk. This talk is about c++ coroutine on the compiler-level.
Audiance may need some knowledge about how to use coroutine and some basic concept about c++ coroutine first.
Is a transcript available for this video?
Lazy evaluation. Cool trick.
Until now i was calling this concept generators, like we have in python. Not used much in python world. Generator should be asymetric coroutine limited to one function body. This is same as javascript async&await - also not called coroutines.
Highly recomend trying out Lua coroutines, which are symetric(allows to switch to any other coro not only yield to caller), also not limited to single function body.
I got spoiled by Lua coroutines and it really bothers me now when someone mistakes simple generators for coroutines.
With coroutines + simple scheduler you can have cooperative threading thingy with all positive threading stuff and none of negative stuff - no mutexes.
Just finding out a lot of conflict in c++ coroutine discussions. Feels like if current c++20 coroutine was just renamed to generators everyone would get along.