C++17 and other future highlights of C++

Re:C++17 and other future highlights of C++ by nly on Thursday March 10, 2016 @04:41PM (#11262622)

Doing networking in the standard library without introducing a proper async framework is just more madness. Polishing off promises and futures, and getting coroutines nailed down, would have made introducing an intuitive network library a doddle.

Instead we'll get something carved out of ASIO, which is a complete mess full of gross unintuitive APIs and callbacks.

[ Parent | on HN ]

Re:C++17 and other future highlights of C++ by gpderetta on Friday March 11, 2016 @05:33AM (#11265785)

What's wrong with ASIO interface? My only issue with it is that once a socket is bound to an io_service it can't be easily rebound to another one.

For many applications where C++ is used, promises and futures introduce unnecessary overhead. On the other hand an ASIO-like interface works just fine.

Additionally, ASIO, and by extension the network proposal, have transparent opt-in support for futures via a special callback type.

[ Parent | on HN ]

Re:C++17 and other future highlights of C++ by nly on Friday March 11, 2016 @10:59AM (#11267327)

Example terrible API: You have to create a socket for a new connection before calling async_accept. Try using this with coroutines.

> opt-in support for futures via a special callback type.

Which is ugly. The coroutines opt-in as well. Coroutines actually have the potential to be faster than callbacks.

[ Parent | on HN ]