Skip to content

unresolved-macro-call triggered for #[derive(...)] whenever a macro_rules! derive macro is defined in the same scope #12734

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

Closed
repnop opened this issue Jul 9, 2022 · 0 comments · Fixed by #14781
Labels
A-macro macro expansion A-nameres name, path and module resolution C-bug Category: bug

Comments

@repnop
Copy link
Contributor

repnop commented Jul 9, 2022

rust-analyzer version: rust-analyzer version: 0.0.0 (5342f47 2022-07-09)

rustc version: rustc 1.62.0 (a8314ef7d 2022-06-27)

relevant settings: none

macro_rules! derive {
    () => {};
}

#[derive(Debug)] // <-- unresolved macro `derive`
pub struct Bar;

compiles successfully, however

@flodiebold flodiebold added A-macro macro expansion C-bug Category: bug labels Jul 11, 2022
@edwin0cheng edwin0cheng added the A-nameres name, path and module resolution label Aug 10, 2022
@Veykril Veykril assigned Veykril and unassigned Veykril Aug 15, 2022
@bors bors closed this as completed in 9b33874 May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-macro macro expansion A-nameres name, path and module resolution C-bug Category: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants