[Boost-bugs] [Boost C++ Libraries] #9001: asio::buffered_stream and family missing future returns

Subject: [Boost-bugs] [Boost C++ Libraries] #9001: asio::buffered_stream and family missing future returns
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-08-16 07:48:58


#9001: asio::buffered_stream and family missing future returns
------------------------------+----------------------------
 Reporter: vinnie.falco@… | Owner: chris_kohlhoff
     Type: Feature Requests | Status: new
Milestone: To Be Determined | Component: asio
  Version: Boost 1.54.0 | Severity: Problem
 Keywords: |
------------------------------+----------------------------
 I'm practically a novice but it seems that
 '''asio::buffered_read_stream''' and '''asio::buffered_write_stream'''
 async operations are missing the futures return value. I believe that
 '''asio::buffered_read_stream::async_read_some''' should have a function
 signature that looks like this:

 {{{
   template <typename MutableBufferSequence, typename ReadHandler>
   BOOST_ASIO_INITFN_RESULT_TYPE(ReadHandler,
       void (boost::system::error_code, std::size_t))
   async_read_some(const MutableBufferSequence& buffers,
       BOOST_ASIO_MOVE_ARG(ReadHandler) handler)
 }}}

 I marked this as "Problem" because it is not possible to wrap either of
 these objects in such a way that they are fully compatible with future
 returns.

 Note that classes like '''asio::basic_stream_socket''' all provide futures
 return values for async functions (when supported by the build
 configuration).

 If I am incorrect please advise me so I can correct my own code because
 this is the model I am following

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/9001>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:13 UTC