Boost logo

Boost :

From: Oliver Kowalke (oliver.kowalke_at_[hidden])
Date: 2021-11-29 17:16:25

Am Mo., 29. Nov. 2021 um 18:09 Uhr schrieb Glen Fernandes via Boost <

> Boost.Coroutine is deprecated, but cannot be removed because of Asio.
> The discussion above implies that Boost.Spawn allows Boost.Coroutine
> to be removed - but I don't understand how because Boost.Asio still
> depends on Boost.Coroutine

My suggestion is that we convince Chris to remove boost::asio::spawn and
add a notice/link to boost.spawn in the asio documentation.

> And Boost.Asio cannot depend on Boost.Spawn since the latter depends
> on Boost.Asio, no? According to Oliver's e-mail above Spawn uses
> io_context from Asio, and that would result in a dependency cycle.
> What am I missing?

I previously made a commit in boost.context that implemented spawn_fiber()
(but introduced a dependency to boost.asio because of io_context).
Via boost::asio::spawn() boost.asio has itself a dependency to
Boost.coroutine depends on boost.context as a foundation for context

Boost list run by bdawes at, gregod at, cpdaniel at, john at