jyn

If it helps, the clap migration guide recommends https://docs.rs/trycmd/latest/trycmd/ for testing the help output. To make it easier to see the differences, you could create a commit only adding trycmd,...

> @jyn514 to clarify, you're suggesting to use `trycmd` just to make a diff between old and a new output and then remove `trycmd` or to integrate it in the...

I'm willing to work on this.

@keithmendozasr I did some code excavation and it looks like [connect_remote](https://github.com/libfuse/sshfs/blob/master/sshfs.c#L1823) is always called on startup. I think [`start_ssh`](https://github.com/libfuse/sshfs/blob/master/sshfs.c#L1217) is called the first time, although there's a branch in connect_remote...

This is basically a duplicate of https://github.com/rust-lang/rust/issues/1998.

> This would required teaching the compiler to do "all simultaneous" (i.e. combinations of cfg'd code) name resolution, and maybe type checking too. It's a big change, but I think...

> There is currently a rustdoc kludge to generate Windows and Unix documentation for std at the same time. Can something like this be extended to work for conditional compilation...

> Provide first-class support for some of the things that people use RUSTFLAGS for today. My main pain point with RUSTFLAGS is https://github.com/xd009642/tarpaulin/issues/416#issuecomment-623150687, which has some niche flags and wouldn't...

> Maybe there can be a way for rustc itself to tell cargo whether an option requires a re-compile? Something like rustc -Z needs-recompile "$RUSTFLAGS". Another option is for cargo...

> you'll need to configure the toolchain if it's non-standard Could you give an example of what you mean? The crate docs say > This crate will automatically detect situations...