31 lines
1.3 KiB
Rust
31 lines
1.3 KiB
Rust
|
use crate::{
|
||
|
|
diagnostics::{Diagnostic, DiagnosticsContext},
|
||
|
|
Severity,
|
||
|
|
};
|
||
|
|
|
||
|
|
// Diagnostic: unresolved-proc-macro
|
||
|
|
//
|
||
|
|
// This diagnostic is shown when a procedural macro can not be found. This usually means that
|
||
|
|
// procedural macro support is simply disabled (and hence is only a weak hint instead of an error),
|
||
|
|
// but can also indicate project setup problems.
|
||
|
|
//
|
||
|
|
// If you are seeing a lot of "proc macro not expanded" warnings, you can add this option to the
|
||
|
|
// `rust-analyzer.diagnostics.disabled` list to prevent them from showing. Alternatively you can
|
||
|
|
// enable support for procedural macros (see `rust-analyzer.procMacro.enable`).
|
||
|
|
pub(super) fn unresolved_proc_macro(
|
||
|
|
ctx: &DiagnosticsContext<'_>,
|
||
|
|
d: &hir::UnresolvedProcMacro,
|
||
|
|
) -> Diagnostic {
|
||
|
|
// Use more accurate position if available.
|
||
|
|
let display_range = d
|
||
|
|
.precise_location
|
||
|
|
.unwrap_or_else(|| ctx.sema.diagnostics_display_range(d.node.clone()).range);
|
||
|
|
// FIXME: it would be nice to tell the user whether proc macros are currently disabled
|
||
|
|
let message = match &d.macro_name {
|
||
|
|
Some(name) => format!("proc macro `{}` not expanded", name),
|
||
|
|
None => "proc macro not expanded".to_string(),
|
||
|
|
};
|
||
|
|
|
||
|
|
Diagnostic::new("unresolved-proc-macro", message, display_range).severity(Severity::WeakWarning)
|
||
|
|
}
|