Tv

If I use `#[cfg(all(kani,test))]` in the library (not `tests/`), `cargo kani` no longer finds the proof (since `test` wasn't set): ``` No proof harnesses (functions with #[kani::proof]) were found to...

`#[cfg(any(kani, test))]` isn't great because then tooling like rust-analyzer complains "use of undeclared crate or module `kani`". I'll test `cargo kani --tests` after some current runs complete..

Would love to. https://github.com/bazil/fuse/issues/58 sits in the queue before it, though, and right now I'm in the middle of a very large refactor to clean up internals.

Are you working on it, or paying for it? Don't be an entitled brat.

The assumptions of the current ReadDir behavior are pretty deeply written into the code I inherited. Step 1 is figuring out the right API, and the implications of that on...

Generally such new features are gated by the negotiated fuse protocol version, which is a trade-off between supporting old systems & non-Linux OSes versus code complexity from handling multiple variants....

Thank you, this looks interesting. I'm traveling for about a week but will get back to testing this after that.

Yeah... the devil is in the details, in this case mostly the interaction with the memory allocation. It's already the part that slows down filesystems most.

Oh, wow. After all this time, I come to the realization that there was no such thing as length-prefixed multiple requests in one memory area. I wonder where I even...

A more flattering, and relevant, benchmark: ``` BenchmarkLookup-12 200000 181849 ns/op 1096 B/op 14 allocs/op ``` This avoids the `NodeID` bookkeeping that `Create` has, and is just a loop over...