Boost 1.66中basic_socket_acceptor接口变更是否为错误？

No, this is not a bug—it’s an intentional API evolution in Boost.Asio to align with modern C++ asynchronous programming patterns and the Executor model. Let’s break down what changed and why:

• The parameter shift explained:

  • In Boost 1.65, basic_socket_acceptor had three template parameters: Protocol, Executor (defaulting to io_context::executor_type), and AcceptHandler (defaulting to void).
  • In Boost 1.66, the AcceptHandler template parameter was removed entirely. Instead of binding the handler type to the acceptor class itself, asynchronous accept handlers are now passed directly as arguments to async_accept() calls.

• Why this change was made:
  This adjustment was part of Boost.Asio’s ongoing effort to align with the C++ standard library’s Executor design. By decoupling the handler type from the acceptor class, the API becomes:

  • More flexible: A single basic_socket_acceptor instance can work with multiple different handler types for asynchronous accepts.
  • More consistent: It matches the pattern used by other Boost.Asio socket types, which had already moved away from handler-specific template parameters.
  • Cleaner: Reduces unnecessary template parameter bloat in the class definition.

• Compatibility note:
  If your code was written for Boost 1.65 and explicitly specified the AcceptHandler template parameter, you’ll need to adjust it when upgrading to 1.66. Simply remove the AcceptHandler argument from the basic_socket_acceptor instantiation, and pass your handler directly to async_accept() as you would with other asynchronous operations.

内容的提问来源于stack exchange，提问作者The Quantum Physicist