Procedural macro used in the crate where it is defined

Reports procedural macros invoked from the same crate that defines them.

Procedural macros (#[proc_macro], #[proc_macro_attribute], and #[proc_macro_derive]) must be compiled before they can be expanded. Because of that, they cannot be used in the crate where they are declared and must be invoked from a separate crate that depends on the defining one.

#[proc_macro]
pub fn my_macro(input: TokenStream) -> TokenStream { input }

my_macro!(); // error: cannot use a procedural macro from the same crate that defines it

Locating this inspection

By ID

Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.

RsProcMacroUsedInTheSameCrate

Via Settings dialog

Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.

Settings or Preferences | Editor | Inspections | Rust

Inspection ID: RsProcMacroUsedInTheSameCrate

Suppressing Inspection

You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:

//noinspection RsProcMacroUsedInTheSameCrate

More detailed instructions as well as other ways and options that you have can be found in the product documentation:

CLion 2026.2

Inspection Details
By default bundled with:	CLion 2026.2,
Can be installed with plugin:	Rust, 262.8701.0

Last modified: 30 June 2026