Robin Lambertz

The reason why the Filesystem trait in rust-fuse uses a Reply argument instead of returning is to allow for asynchronous response. If I'm understanding this feature request correctly, this would...

`error`/`ok` take `self` by value, so you can't call them multiple times.

If rust-fuse moves to `tokio`/`mio`, then maybe it could make sense to return a `Future`. But in the interim, I don't think it makes too much sense as it only...

The point is that if it's passed as a parameter, the driver can then push the request/response to a thread pool or an event queue. `rust-fuse` would still block on...

On the linux kernel, at least, [the fd implements `poll`](https://github.com/torvalds/linux/blob/master/fs/fuse/dev.c#L2233) and so is usable inside epoll/select/poll calls. The same might not be true of other implementations though.

I came accross https://github.com/anowell/netfuse just now, which seems to be good enough for most basic operations (it's missing lots of ops though).

Instead of exposing the Fd, it might be possible to expose an opaque object implementing [`mio::Evented`](https://docs.rs/mio/0.6.9/mio/event/trait.Evented.html). This would allow it to be used in mio as such : ```rust let...

Yeah windows support definitely involves a bit more logic, but it'd be really nice to have it there too. I think it could be done using a fairly simple process...

This can now safely be merged. The new version of npdmtool/elf2kip was published on pacman.

> Yeah, I am just trying to look at it from the shoes of users working on proprietary software where it is common to strip it and clean/obfuscate/tweak binaries in...