As the following example demonstrates, cppcoro::shared_tasks become cppcoro::tasks when propagating through cppcoro::schedule_on. Is this intended behaviour?
auto f() -> cppcoro::shared_task<int>
{
co_return 0;
}
auto tp = cppcoro::static_thread_pool{};
auto g = cppcoro::schedule_on(tp, f()); // g is a cppcoro::task<int&>
As the following example demonstrates,
cppcoro::shared_tasks becomecppcoro::tasks when propagating throughcppcoro::schedule_on. Is this intended behaviour?https://godbolt.org/z/e3oKBG