Cargo Calls for Testing

[epage]

There are several unstable Cargo features without an RFC that we would like help in testing. As there is no documented process without an RFC, I figured I'd create an issue here

rust-lang/cargo#11123: cargo install --dry-run

• Instructions: cargo install --dry-run cargo#11123 (comment)

rust-lang/cargo#14520: native completions for cargo

• Instructions: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#native-completions

[bennyvasquez]

Hi there! Thanks for creating the issue. As you said, there's no good place for this to live right now. Is this something that you could phrase into a request for contributions?

[epage]

Is there a reason that the Call for Testing section wouldn't work for this? Is there a reason to limit it to just RFCs? Many teams have adopted different processes (ACP, MCP, etc) where an RFC may never be involved yet it can still be useful to test.

[bennyvasquez]

I'm honestly not sure it fits there, but that section is managed by another editor. @U007D what do you think about potentially adding these sorts of things to the calls for testing? I think I remember you were considering expanding it, but I don't remember if you ever did.

[epage]

Ah, looks like this came up in #5222. I've added a label for the Cargo repo: https://github.com/rust-lang/cargo/labels/call-for-testing

If Cargo could be added to the query, that'd be great!