-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
prelude path should not appear in error messages #56861
Copy link
Copy link
Open
Labels
A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lintsC-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.D-papercutDiagnostics: An error or lint that needs small tweaks.Diagnostics: An error or lint that needs small tweaks.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Metadata
Metadata
Assignees
Labels
A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lintsC-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.D-papercutDiagnostics: An error or lint that needs small tweaks.Diagnostics: An error or lint that needs small tweaks.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
(Split off from discussion on #56188.)
There are a few places where the path
std::prelude::v1appears in diagnostic messages.I argue that this is bad because the point of the prelude is to relieve the ordinary programmer from having to think about where necessities like
SomeandVeclive; the modulestd::prelude::v1is an implementation detail that should be mentioned in places like the Book, but which I don't want to see cluttering up error messages.We are manually stripping off the
std::prelude::v1::in a couple places (one, another proposed in open PR #56188), but we should:std::prelude::v1::for all diagnostic messages