-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Open
Labels
A-cliArea: Command-line interface, option parsing, etc.Area: Command-line interface, option parsing, etc.A-documenting-cargo-itselfArea: Cargo's documentationArea: Cargo's documentationC-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-needs-infoStatus: Needs more info, such as a reproduction or more background for a feature request.Status: Needs more info, such as a reproduction or more background for a feature request.
Description
Problem
Hello there, when cargo checking features that are invalid I get an exit status of 101 and I went to:
https://github.com/rust-lang/cargo/blob/master/src/doc/src/commands/cargo-check.md
To understand this exit code compared to others it would be nice to have a table of the expected exit codes and their meaning.
Proposed Solution
| Code | Meaning |
|---|---|
| 0 | Check Passed |
| 101 | Invalid Features |
| X | Meaning X |
Notes
Where could I find the returned codes, I would be happy to make this change, however the experienced contributor reading this could likely do so in 10 seconds.
Metadata
Metadata
Assignees
Labels
A-cliArea: Command-line interface, option parsing, etc.Area: Command-line interface, option parsing, etc.A-documenting-cargo-itselfArea: Cargo's documentationArea: Cargo's documentationC-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-needs-infoStatus: Needs more info, such as a reproduction or more background for a feature request.Status: Needs more info, such as a reproduction or more background for a feature request.