Michal 'vorner' Vaner

Sorry for the late response. First, the more direct answer to your question. If the previous one registered a signal action/signal handler the unix way (`libc::signal` or similar), then their...

First of, I prefer to keep the Cargo.lock in the repo. I prefer to update manually. Don't worry, the downstream crates don't consider Cargo.lock from libraries, it's only from development...

> I don't understand why the crate uses futures and aliases the dependencies. If I remember correctly (it's a long time ago), it was in times when tokio didn't have...

Hello I understand the argument. Nevertheless, this would be a breaking change and it doesn't seem worth doing a „big version“ jump because of that. Let me note, however, that:...

:thinking: This approach seems rather fragile. I mean, we can set up some protocol to talk between these two crates, like the exclusive flag you mentioned. But that doesn't stop...

Nevertheless, you make a point that SIGBUS is, in fact, a signal somewhat dangerous to mess with. I'll have to think about what are the (safety / soundness) implications with...

> that third crate would have to be using unsafe code somewhere. I can't stop that, any more than I can stop a third-party crate from doing anything else unsafe....

Yes, I know, there's even a crate for that (clap-verbosity-flag, I think). However, if I want to set the logging to debug, having to count how many `-v`s I need...

Hello. I'd like this to move forward (especially because of `Box`). Is there anything I could do to help to move forward?

Yes, that's what I think too. I had the idea of looking at some other language with a wire server how it does that (spy on it through wireshark), but...