You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not yet! -- we're aiming for parity with the standard library, so this would be an API we may not want to expose directly from async-std. But I agree we should definitely have a good way of handling signals that's compatible with async-std.
Probably a good way to start would to be to look at signal-hook and see if we can make it compatible with async-std.
Following up on #293. signal-hook crate supports mio by implementing and exposing dyn Evented which in theory could be plugged into a async_std::net::Watcher
I notice @0b01 you says signal-hook implement Evented, so I try to write a crate async_signals to handle signal in async fn. Also I read the async_std::net::Watcher, it seems is not so hard to add signal into async-std
Activity
yoshuawuyts commentedon Oct 10, 2019
Not yet! -- we're aiming for parity with the standard library, so this would be an API we may not want to expose directly from
async-std
. But I agree we should definitely have a good way of handling signals that's compatible withasync-std
.Probably a good way to start would to be to look at
signal-hook
and see if we can make it compatible withasync-std
.0b01 commentedon Oct 11, 2019
Following up on #293. signal-hook crate supports mio by implementing and exposing
dyn Evented
which in theory could be plugged into aasync_std::net::Watcher
Sherlock-Holo commentedon Mar 8, 2020
I notice @0b01 you says
signal-hook
implementEvented
, so I try to write a crate async_signals to handle signal in async fn. Also I read the async_std::net::Watcher, it seems is not so hard to add signal intoasync-std