Andreas Neuhaus

The unmount method is private since resources are meant to be managed by RAII and the FUSE filesystem lives as long as the `Session` exists. Dropping the `Session` will unmount...

We could also think about adding signal handling to `rust-fuse`. With `chan-signal` it seems pretty easy and could be enabled/disabled via a cargo feature flag. This sounds convenient, however I'm...

Interesting. The kernel driver shouldn't send requests with this opcode at all since we're requesting ABI 7.8 in the FUSE_INIT reply.

Sadly I didn't get much time over christmas to work on fuse-rs. This branch is basically well prepared for async/await. It's still missing some essential functionality like the session loop...

I agree that such a template would be nice. I always wanted to write a mirror example (a fuse fs that simply mirrors another existing path). This sounds similar to...

I'd also really like to see a more idiomatic API. Back when I wrote the Filesystem trait, it wasn't really clear how cases like these should be handled idiomatically. I...

I've been thinking about how to make the API more idiomatic and have come up with some ideas. We need to keep ensured that (a) the actual implementation can only...

The reply parameter doesn't make it async. The key thing is, that it doesn't prevent you from making it async. Passing the reply parameter gives the implementor freedom to either...

> But the caller can always spawn a thread ... The caller of the `Filesystem` methods is the session loop of rust-fuse that dispatches requests from the kernel driver to...

I did some cleaning and improvements on the code in the `modernize` branch, which now also has a new version of the `Filesystem` trait that's using return values for replying:...