rami3l
rami3l
@Psy-Kai From my personal experience, `podman` is known to have subtle bugs compared to `docker`, and that's why I have both on my workstation. [^1] Would you mind giving `docker`...
Looks like a perfect final step for #3790! I've added this to the task list.
@djc Not yet; it's about the `download` crate. The end goal, of course, is that `download` crate becomes a part of our single crate. I've done that linking for you.
@0xg0nz0 Hello, thanks for filing this issue! It is true that both `miri` and `rustc-codegen-cranelift` are nightly-exclusive components as for now, so `complete` failing to install might indicate an inconsistency...
@pietroalbini Looking towards the end of the *stable* `multirust-channel-manifest.toml` I have found the following section: ```toml [profiles] complete = ["rustc", "cargo", "rust-std", "rust-mingw", "rust-docs", "rustfmt-preview", "clippy-preview", "rust-analyzer-preview", "rust-src", "llvm-tools-preview", "rust-analysis",...
Probably related - https://github.com/rust-lang/rustup/issues/4073
I highly doubt whether we can fix this without regressing #4073, but if you can, using commas would be a better option for a quick fix.
The expected behavior on our side is, of course: ```console -c a,b d => args=[d] c=[a, b] -c a -c b d => args=[d] c=[a, b] d -c a b...
@epage Thanks for your detailed analysis. Immediately after writing that comment I have realized there are a lot of ambiguities in my examples. I have also contributed to `clap`'s painstakingly...
@epage Thanks a lot! I think that's all the information I'll need for now. > The usage was never clearly defined. @crawfxrd You are right... That's why I've changed the...