Road to 1.0.0

[jbaldwin]

• IOCP support (draft) #359 Windows IOCP/poll support
• EMSCRIPTEN poll support
• coro::net::dns::resolver use non-deprecated c-ares functions #387 Modernize c-ares usage
• error: unknown argument: '-fconcepts' [clang-diagnostic-error] #364 Remove -fconcepts/-fcoroutine compiler support, dropping the very old compilers that supported coroutines seems prudent.
• Change std::chrono::milliseconds parameters to templated parameter #308 Template chrono usages for consistent API usage
• Make coro::net::* use concepts::io_executor #239 Template io_executor usages for consistent API usage
  • Rename io_executor to poll_executor? This change would go hand-in-hand with renaming io_scheduler.
• Support for file IO? #171 File IO
  • This could be tricky, e.g. epoll doesn't support proper read/write file notifications, would require a backing thread pool most likely.
• New feature: awaitable generator #158 awaitable generator
• Rename coro::io_scheduler to coro::scheduler
• Rename LIBCORO_FEATURE_NETWORKING -> LIBCORO_FEATURE_HAVE_POLL

This list is not exhaustive but trying to nail down what a good set of features/changes should get this project to a v1.0.0. Please leave comments or thoughts on other items to add to this list.

[PyXiion]

I think it's better to get rid of the polling concept completely in the user-facing API and encapsulate it inside write/read methods, since Windows and emscripten don't support polling.