From my perspective, I already have something that's using condition_variables. I want to straight adapt it into coroutines as much as
Hi Vinnie, I'd like to think that my question was legitimate and clear. "If only there was something like that" sounds snarky to me and doesn't answer the question at all. Maybe behind the scenes it might look like there's just another function to call when complete. But how do I go from *there* to... resuming a different coroutine which is waiting for that function to complete? possible. I don't want to "call a function to indicate something has finished". That's far more friction required. I spent a couple hours poking around asio documentation and didn't find a solution. To be fair, there's a ton of things in asio that are described with a C++ declaration and zero description whatsoever of what it does. So perhaps it is already solved. So maybe the problem already is solved and I just didn't see it. Can you point me to exactly a coroutine-enabled condition_variable? Or perhaps you can point me to specific documentation to read? Thanks, Keith On Tue, Dec 5, 2023 at 7:48 PM Vinnie Falco via Boost-users < boost-users@lists.boost.org> wrote:
On Tue, Dec 5, 2023 at 5:43 PM Keith Bennett via Boost-users < boost-users@lists.boost.org> wrote:
One of the things that keeps cropping up in the ability to notify another function that something has finished.
So... "call a function to indicate something has finished?" If only there was something like that...
Thanks
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users
-- Keith Bennett