Alan Somers
Alan Somers
I like this idea. And as far as I'm concerned, graphing only local dependencies would actually be better than graphing global modules too. I actually wrote my own version of...
Here's a newer crate than produces nice module graphs: https://github.com/regexident/cargo-modules
Whatever the final solution is, the docs should definitely tell the user what he must do to use `spawn_mount` safely.
I've been working on a new approach to testing crates that use rust-fuse. I'm using [`mockall`](https://github.com/asomers/mockall) to create mock versions of each Request and Reply type. Then I have to...
I thought it was something like that. If it can't be fixed, cie la vie.
Ouch, that's a doozy. Thanks for pointing me to it, regexident.
I"m using a Ryzen 5950X, and I also see lots of variability. But pinning the process to a single core using the `cpuset` command does eliminate most of the variability....
cool! Thanks for the tip.
Also, it would be good to show an example of documenting the generated struct. Placing doc comments above the `pub struct` line seems to work.
The current documentation isn't very clear. I didn't realize that I could attach attributes until I had read the source. Examples would be very helpful.