4 releases

0.10.1 Jul 10, 2023
0.10.0 Mar 22, 2023
0.9.1 Nov 1, 2020
0.9.0 Oct 10, 2020

#20 in Procedural macros

Download history 43874/week @ 2023-06-06 41087/week @ 2023-06-13 42889/week @ 2023-06-20 42045/week @ 2023-06-27 48022/week @ 2023-07-04 47621/week @ 2023-07-11 51251/week @ 2023-07-18 50234/week @ 2023-07-25 47822/week @ 2023-08-01 48905/week @ 2023-08-08 49652/week @ 2023-08-15 49328/week @ 2023-08-22 42986/week @ 2023-08-29 47476/week @ 2023-09-05 52538/week @ 2023-09-12 44383/week @ 2023-09-19

196,283 downloads per month
Used in 601 crates (11 directly)

MIT/Apache

25KB
389 lines

proc-macro2-diagnostics   crates.io docs.rs

Diagnostics for stable and nightly proc-macros!

Usage

  1. Depend on the library in your proc-macro.
[dependencies]
proc_macro2_diagnostics = "0.10"
  1. Import SpanDiagnosticExt and use its methods on a proc_macro2::Span to create Diagnostics:
use syn::spanned::Spanned;
use proc_macro2::TokenStream;
use proc_macro2_diagnostics::{SpanDiagnosticExt, Diagnostic};

fn my_macro(input: TokenStream) -> Result<TokenStream, Diagnostic> {
    Err(input.span().error("there's a problem here..."))
}
  1. If there's an error, emit the diagnostic as tokens:
extern crate proc_macro;

pub fn real_macro(tokens: proc_macro::TokenStream) -> proc_macro::TokenStream {
    match my_macro(tokens.into()) {
        Ok(tokens) => tokens.into(),
        Err(diag) => diag.emit_as_expr_tokens().into()
    }
}

This does the right thing on nightly or stable.

Caveats

On stable, due to limitations, any top-level, non-error diagnostics are emitted as errors. This will abort compilation. To avoid this, you may want to cfg-gate emitting non-error diagnostics to nightly.

Colors

By default, error messages are colored on stable. To disable, disable default features:

[dependencies]
proc_macro2_diagnostics = { version = "0.10", default-features = false }

The compiler always colors diagnostics on nightly.

License

Licensed under either of the following, at your option:

Dependencies

~0.4–0.8MB
~20K SLoC