What's wrong with ASIO interface? My only issue with it is that once a socket is... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		gpderetta on March 11, 2016 \| parent \| context \| favorite \| on: C++17 and other future highlights of C++ 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.

nly on March 11, 2016 [–]

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.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact