Denis Blank

Ok, I totally agree with you now. I'm not sure if this is easy to fix, since in general it is not explicitly specified by the library design when the...

Sorry for my late response. I have seen this issue as you created it. Thank you for your report. I will take a look on it in the following days.

I have taken a look at your example and I had to fix a few issues with it: ```cpp #include #include #include #include #include #include #include #include #include #include #include...

> When using coroutines with Asio wouldn't it be better to use Asio's built-in awaitable or coro objects ? Or have people found that the continuable object has less overhead...

> Awesome. Do you know if continuable coroutines and asio coroutines mix well ? For **basic** usage scenarios you can safely mix and match most coroutine libraries and their awaitable...

@Spongman can you confirm that removing the edge-cases in your example fixes the mentioned issues?

Hi, the documentation also states that it requires function2 and it recommends adding both libraries as git submodule (https://naios.github.io/continuable/installation.html#installation-installation-copy): ``` git submodule add https://github.com/Naios/continuable.git git submodule add https://github.com/Naios/function2.git // ......

Thanks for your report. It might be possible that `to_future` is missing the correct logic for the cancellation.

@geiseri Could you maybe provide a code example what you have tried so far?

I second what @Spongman says. Tracing the destructor of your shared_ptr object through a debugger is probably your best option. Additionally I have to add that the callable that you...