Cargo should abort with one error when target does not exist #111909
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Code
Current output
Desired output
Rationale and extra context
When you have a lot of code or using a lot of crates the first line get covered by the terminal and you get mystified. For example adding a dependency increase the number of error lines a lot, few more dependencies and it will get over the terminal scroll limit.
Other cases
Anything else?
Sometimes when compiling for a target that is not installed, a long list errors is printed. The user won’t know the reason he cannot scroll up past the terminal limit.
If possible, I think it will be easier if cargo prints that the target does not exist.
I have been bitted by this issue few times, and I had to help people with this issue.
The text was updated successfully, but these errors were encountered: