You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wrapping my custom socket type in the boost::asio::ssl::stream wrapper. Building with boost-1.66-rc1 I get a compilation error caused by the way the ssl wrapper use read_some().
According to the documentation the function takes a MutableBufferSequence, defined here
to have a const_iterator type and begin() and end() functions, to iterate the buffer sequence.
However, in the boost-1.66-rc1 version of asio's ssl stream wrapper, it calls read_some() (here) with a boost::asio::mutable_buffer (i.e. not a sequence). It passes core.input_buffer_ which is defined here.
As far as I can tell, core.input_buffer should be of type boost::asio::mutable_buffers_1. Making this change makes my program build again.
The text was updated successfully, but these errors were encountered:
I'm wrapping my custom socket type in the boost::asio::ssl::stream wrapper. Building with boost-1.66-rc1 I get a compilation error caused by the way the ssl wrapper use
read_some()
.According to the documentation the function takes a MutableBufferSequence, defined here
to have a
const_iterator
type andbegin()
andend()
functions, to iterate the buffer sequence.However, in the boost-1.66-rc1 version of asio's ssl stream wrapper, it calls
read_some()
(here) with aboost::asio::mutable_buffer
(i.e. not a sequence). It passescore.input_buffer_
which is defined here.As far as I can tell,
core.input_buffer
should be of typeboost::asio::mutable_buffers_1
. Making this change makes my program build again.The text was updated successfully, but these errors were encountered: