Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Commits on Jul 23, 2024

  1. Unify wording of "failed to resolve" errors with "cannot find" resolu…

    …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
    ```
    estebank committed Jul 23, 2024
    Configuration menu
    Copy the full SHA
    2abb31d View commit details
    Browse the repository at this point in the history