No more cycles going forward
Boost 1.77.0 released with no dependency cycles between libraries. This wasn't easy to achieve and we want to preserve it, going forward. We should not regress and allow libraries to introduce dependency cycles in any future Boost release. i.e. Doing so should be considered a release blocker. Currently, such a regression exists (introduced last month in Context): Asio -> Coroutine -> Context -> Asio It should be fixed before we lock the branches for the 1.78 release, or we should not take this change in the release. Glen
On 10/16/21 12:48 AM, Glen Fernandes via Boost wrote:
Boost 1.77.0 released with no dependency cycles between libraries.
This wasn't easy to achieve and we want to preserve it, going forward. We should not regress and allow libraries to introduce dependency cycles in any future Boost release. i.e. Doing so should be considered a release blocker.
Currently, such a regression exists (introduced last month in Context): Asio -> Coroutine -> Context -> Asio
It should be fixed before we lock the branches for the 1.78 release, or we should not take this change in the release.
Perhaps an issue for Boost.Context is in order. It seems backwards for it to depend on ASIO.
Am Sa., 16. Okt. 2021 um 00:10 Uhr schrieb Andrey Semashev via Boost < boost@lists.boost.org>:
On 10/16/21 12:48 AM, Glen Fernandes via Boost wrote:
Boost 1.77.0 released with no dependency cycles between libraries.
This wasn't easy to achieve and we want to preserve it, going forward. We should not regress and allow libraries to introduce dependency cycles in any future Boost release. i.e. Doing so should be considered a release blocker.
Currently, such a regression exists (introduced last month in Context): Asio -> Coroutine -> Context -> Asio
It should be fixed before we lock the branches for the 1.78 release, or we should not take this change in the release.
Perhaps an issue for Boost.Context is in order. It seems backwards for it to depend on ASIO.
reverted
On Sat, Oct 16, 2021 at 2:58 AM Oliver Kowalke wrote:
Am Sa., 16. Okt. 2021 um 00:10 Uhr schrieb Andrey Semashev:
On 10/16/21 12:48 AM, Glen Fernandes via Boost wrote:
Currently, such a regression exists (introduced last month in Context): Asio -> Coroutine -> Context -> Asio It should be fixed before we lock the branches for the 1.78 release, or we should not take this change in the release.
Perhaps an issue for Boost.Context is in order. It seems backwards for it to depend on ASIO.
reverted
Thanks Oliver. Glen
participants (3)
-
Andrey Semashev -
Glen Fernandes -
Oliver Kowalke