The fact that the classes mentioned in the title are in details does not allow us to customize boost.asio normally. In the latest versions, it has become possible to transfer scheduler_task to the scheduler, but this is all still in detail. Therefore, it is not possible to create a custom io_service. I don’t want to rely on an unstable API in my project.
Perhaps there are plans to transfer this api to public namespaces?
The fact that the classes mentioned in the title are in details does not allow us to customize boost.asio normally. In the latest versions, it has become possible to transfer scheduler_task to the scheduler, but this is all still in detail. Therefore, it is not possible to create a custom io_service. I don’t want to rely on an unstable API in my project.
Perhaps there are plans to transfer this api to public namespaces?