4 Mar
2018
4 Mar
'18
4:04 p.m.
On Fri, Mar 2, 2018 at 2:26 PM, Niall Douglas via Boost
ASIO's supremacy has changed what the C++ user base expect when they see an error_code& API. They expect that all failures will be indicated by said error_code&.
Asio functions which have `error_code&` in their signature can still throw exceptions. Not sure why you think otherwise. Regards