Ed Page
Ed Page
> I think this should eventually wind up [in cargo metadata] even though I didn't mention it in this RFC (@epage does it seem reasonable to add it?). So while...
@tgross35 > The most elegant schema would be to mirror these tables directly into metadata. > That is, update: > > `` > > To be something like: > >...
@weihanglo and @kornelski I moved your conversation into a thread in the hopes that it will make it easier to follow
FYI I removed T-rustdoc from this RFC because this is the Cargo portion split out of #3421 which is now just T-rustdoc's side. T-rustdoc's input in this RFC is still...
> > Do you mean crates within a workspace wanting to use private features for other crates in the workspace? If so, I previously had a `--allow-private-features` flag as part...
> Another thought is the (current) inability to squelch the warning. Let's say I update a dependency and start getting the warning, but I can't change it right now. That...
#4551 styled help output to match Cargo #4556 for `rustup show` #4557 for `rustup update` #4558 for `rustup * list` #4559 for `rustup toolchain list` (which is different than the...
#4574 explores an alternative layout for `rustup check`
`#[toml_edit]` attributes would not work with serde. What you can do is serialize to a `DocumentMut` (instead of a `String`) and then edit the document to suit your needs. `VisitMut`...
To be clear, you aren't wanting blank lines between groups of subcommands but after every subcommand? We have #1553 for the former. As for blank lines between every subcommand, what...