Tracking Issue for default-run

[ehuss]

Original Issue: #2200
Implementation PR: #5710
Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#default-run

Summary

The default-run feature provides a way to specify which binary will be run by default by cargo run when there are multiple binaries.

[package]
default-run = "foo"

Unresolved issues

• The error message when default-run specifies a non-existing binary is not great (it just says "no bin target named …"). I think it should point the user to the default-run definition.

[ehuss]

I'd like to propose stabilizing this feature.

@rfcbot merge

Stabilization Target: 1.37 — Release date August 15th 2019

This feature has been around for almost a year. There haven't been any issues, and I can't think of any changes that would be needed. It is fairly straightforward. It is not a high-demand feature, but there are some projects using it, and presumably more would use it if it weren't nightly-only.

The error messages should be cleaned up a little when it is stabilized. Documentation will also be need to be updated.

[rfcbot]

Team member @ehuss has proposed to merge this. The next step is review by the rest of the tagged team members:

• @Eh2406
• @alexcrichton
• @ehuss
• @joshtriplett
• @nrc
• @withoutboats

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.

[joshtriplett]

@rfcbot reviewed

[rfcbot]

🔔 This is now entering its final comment period, as per the review above. 🔔