Skip to content

rustc should not try to analyze the crate after "multiple candidates" messages #118130

Open

Description

#118129 is an example of an issue that somehow leads to "multiple candidates" errors for each rustc crate. However, it took hours to get to that conclusion, because rustc shows >1800 errors saying all sorts of things could not be found. The actual signal is drowning in that noise. This is also fairly common when something goes wrong with the sysroot and it has multiple core/std candidates and imports none of them: all one can see are hundreds of errors saying that some lang item is missing.

It would be better if rustc stopped after crate loading when there was such a "multiple candidates" error, or at least didn't show all the follow-up messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    A-diagnosticsArea: Messages for errors, warnings, and lintsC-bugCategory: This is a bug.D-verboseDiagnostics: Too much output caused by a single piece of incorrect code.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions