Earlier quoted context omitted.
Having only briefly looked through the code base of libgo. It looks like they use boost::context, which is the only good stackful coroutines implementations I've come across. Not being familiar with your project I'm slightly confused about the statement of "hundreds of thousands of short-lives micro-tasks". This is usually a no-go in case of stackful coroutines, as you would waste too much memory as well as have a lo…
it does not look like it's using boost::context. At least I never saw it in runtime. It's using its own asm routines for save/restore the context.
C++20: Building a Thread-Pool with Coroutines
61–63 of 63 posts
Re: C++20: Building a Thread-Pool with Coroutines
#62Earlier quoted context omitted.
it does not look like it's using boost::context. At least I never saw it in runtime. It's using its own asm routines for save/restore the context.
As far as I can tell the developer is using Fibers on Windows and boost::context on all other operating systems. You can see that he has a forward declaration in "libgo/context/fcontext.h" and then links against the respective boost assembly files in the CMakeLists.txt.
Re: C++20: Building a Thread-Pool with Coroutines
#63Earlier quoted context omitted.
Good way to put what’s wrong with Python async and probably by extension C++ too. The sync-async in both direction need to be symmetrical for it to make sense. Right now in Python async can interact with Python sync quite comfortably but the opposite direction is a literal black hole. I have had to read up on how sync can interact with async multiple times but I’m still not sure what is the idiomatic way and it alway…
No, it is not you. https://journal.stuffwithstuff.com/2015/02/01/what-color-is-...
So glad that this has been well pointed out. Oof big relief