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

macro_expanded_macro_exports_accessed_by_absolute_paths lint links to dead Rust issue #91842

Closed
Kampfkarren opened this issue Dec 13, 2021 · 2 comments
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.

Comments

@Kampfkarren
Copy link
Contributor

Given the following code:

macro_rules! parent {
    () => {
        #[macro_export]
        macro_rules! child {
            () => {}
        }
    }
}

parent!();
crate::child!();

The current output is:

   Compiling playground v0.0.1 (/playground)
error: macro-expanded `macro_export` macros from the current crate cannot be referred to by absolute paths
  --> src/lib.rs:11:1
   |
11 | crate::child!();
   | ^^^^^^^^^^^^
   |
   = note: `#[deny(macro_expanded_macro_exports_accessed_by_absolute_paths)]` on by default
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
   = note: for more information, see issue #52234 <https://github.com/rust-lang/rust/issues/52234>

Going to #52234 at the link provided gives a 404.

@Kampfkarren Kampfkarren added 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. labels Dec 13, 2021
@Kampfkarren
Copy link
Contributor Author

The nightly reference links to #53495.

@Kampfkarren
Copy link
Contributor Author

Not sure why but looks like 52234 is back...? 🤷‍♀️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
None yet
Development

No branches or pull requests

1 participant