-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unify wording of "failed to resolve" errors with "cannot find" resolution errors #128086
base: master
Are you sure you want to change the base?
Conversation
…tion errors * Use the same wording for all macro resolution errors * specify the scope in which the resolution failure happened Before ``` error[E0433]: failed to resolve: `crate` in paths can only be used in start position --> $DIR/crate-path-non-absolute.rs:5:22 | LL | let s = ::m::crate::S; | ^^^^^ `crate` in paths can only be used in start position ``` after ``` error[E0433]: cannot find module `crate` in module `m` --> $DIR/crate-path-non-absolute.rs:5:22 | LL | let s = ::m::crate::S; | ^^^^^ `crate` in paths can only be used in start position ```
Some changes occurred in src/tools/clippy cc @rust-lang/clippy |
Split off from #126810. "Hide whitespace" will aid in seeing mostly "true" changes. The amount of files being touched is a consequence of the blast radius the diagnostic has. Happy to hear about other potential alternatives for what the output should be instead. |
The job Click to see the possible cause of the failure (guessed by this bot)
|
Blocking on the wording discussion in #128080 (comment). |
☔ The latest upstream changes (presumably #128169) made this pull request unmergeable. Please resolve the merge conflicts. |
Before
after
r? @petrochenkov