Michal 'vorner' Vaner
Michal 'vorner' Vaner
With the addition of Exfiltrator, the async adapters were changed to support that. But the `Stream` trait is still implemented on the `Signals` type alias, not on `SignalsInfo` type, which...
As discussed in #78, the current situation in which a library may „steal“ a signal that usually has a default handler can be undesirable. This should be something that is...
The current documentation states how one could emulate the individual default signal handlers. This works, but is a bit unergonomic. The idea is to provide a wrapper function that takes...
Signal hook uses the low-level `c_int` to represent signal numbers, because signal numbers are somehow "open" enum ‒ it's not clear what signals might be available on whatever platform someone...
This means going over it, documenting all the safety invariants and such.
The `iterator::backend::Handle` has `add_signal`, but no `remove_signal`. This is a bit inconsistent and it turns out people would find it useful (see #63). By implementing it on `Handle`, one would...
The crate is very low-level and deals with quirky APIs different OS implement slightly differently. It would be nice to have them covered on CI. At least these come into...
Sometimes it is nice to have an array indexed by signals preallocated. To do that, we would need to know what the max signal number on a given platform is....
Steps to reproduce: * Make a clean checkout of this repository (without `Cargo.lock`). * Run `cargo test`. I'm getting compile errors (cannot find macro prop_oneof) from the test. I suspect...
Hello I was trying to use `peel-ip` for something and hit some setbacks. I was thinking a bit about how to fix them, and identified few areas in the API...