Migration to another implementation of asio

[eternal-sorrow]

If is possible for libtorrent to migrate to chriskohlhoff/asio and eventually drop the Boost dependency?

[arvidn]

Anything's possible, I don't see any upside. You would need to find replacements for all the other boost libraries the libtorrent depend on as well. multi index container is a big one for instance.

[eternal-sorrow]

This is the problem with big libraries like boost. If you bring it for one feature, you might as well use it also for other convenient features. Fast-forward, you end up being totally bound to it with no way to easily get rid of it.

[arvidn]

The flip-side is that you can implement your own multi-index container, instead of the actual library. I suspect your aversion to dependencies is the difficulties it causes in build systems. I don't think the solution is to have fundamental libraries be re-implemented everywhere.

[arvidn]

This is the problem with big libraries like boost. If you bring it for one feature

libtorrent depended on boost before asio was a thing btw. So, what might that original feature have been, that boost was brought in for?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.