I’ve recently learnt about coroutines, and got excited as I maintain several async libraries, for which to support coroutines for at least the base library -the task scheduler-.

I’ve recently learnt about coroutines, and got excited as I maintain several async libraries, for which to support coroutines for at least the base library -the task scheduler-.

Closed 18 mins ago.

On cppreference I read the following (emphasis mine):

There’s not really much when searching for c++coroutine “optional”, but from the final part of this answer I’d deduce that std::optional can’t be made a coroutine non-intrusively. However, I want to understand the details of this fact.

Suppose I have two coroutines, coroutine_a and coroutine_b. In coroutine_a it calls:

Let an Awaiter return a handle, H, in its await_suspend.

Let task foo() be a coroutine. I want to support:

I was playing with cpprefernce’s code pulling the out_thread into resuming_on_new_thread coroutine:

In C++ coroutines, the promise type’s final_suspend member function can return any arbitrary awaitable type, though commonly it’s std::suspend_always which leaves the responsibility to someone else to destroy the coroutine, or std::suspend_never which automatically destroys the coroutine. The latter seems to be a special case, since normally it is not allowed to resume a coroutine that is at its final suspend point. In my testing though, it seems like this special behavior is not uniformly applied.