Curtis Maves
Curtis Maves
`AsRawFd` is implemented for `DuplexConn` which gives the receiving `RawFd`. If your using `RpcConn`, you can use `RpcConn::conn()` to get the underlying `DuplexConn` first.
It is definitely possible to implement this as async without the send/recvmsg being async. All syscalls are "synchronous". Async libraries like async-std and tokio workaround this in a few different...
I've created an async API in a crate built on top of this crate. It can be found [here](https://github.com/cmaves/async-rustbus). It is unreleased, but it almost ready to go. It signal...
Could this instead be implemented by just relying on the behavior of signals? If you're trying to handle a graceful shutdown, and presumably have set a signal handler for SIGTERM...
Fair enough, I'm sold on this use case. Hopefully this can be implemented without degrading performance if you use only non-blocking calls in the first place ( I would think...
I made an issue on the monero repo. https://github.com/monero-project/monero/issues/3189
I'll leave this issue open until it is either fixed on the upstream or fixed in kasisto itself