Re: [Boost-users] ASIO: custom service which works with spawn/yield

On 25 July 2018 at 17:13, Vinnie Falco via Boost-users wrote:

On Wed, Jul 25, 2018 at 7:25 AM, Cristian Morales Vega via Boost-users wrote:

...

boost::system::error_code ec = boost::asio::error::already_started; boost::asio::post( boost::beast::bind_handler(std::move(init.completion_handler), std::move(ec)));

Two things you can try:

1. Don't use move on ec:

boost::system::error_code ec = boost::asio::error::already_started; boost::asio::post(boost::beast::bind_handler( std::move(init.completion_handler), ec);

2. Try the tip of the Beast master branch (or the 1.68 beta). In particular, this change:

https://github.com/boostorg/beast/commit/f948c9cbe57552f2a2b1306235ba578584b...

Unfortunately it makes no difference. Actually even using "std::bind(std::move(init.completion_handler), ec);" I still get "system:0".