Atualmente está em desenvolvimento a lib
pike e
zap que são voltados a async-IO, porém trazendo perspectivas diferentes, como cita o autor do pike:
What is the difference between pike and zap?
"Pike provides asynchronous wrappers around certain OS syscalls and makes sure their usage is consistent cross-platform, like for sockets/signals/events.
Zap can be plugged together with Pike to have the driving of syscalls in an async manner done on multiple threads at once (via Zap's scheduler plugged into a thread pool).
I guess an equivalent mannerism in a different programming language would be netpoll in Go being pike, and the Go scheduler/runtime being Zap.
In Rust, Mio would be Pike and Tokio provides a scheduler on top of Mio." - lithdew