2 releases

0.9.1 Nov 1, 2020
0.9.0 Oct 10, 2020

#98 in Procedural macros

Download history 97/week @ 2020-10-05 300/week @ 2020-10-12 1209/week @ 2020-10-19 1390/week @ 2020-10-26 1531/week @ 2020-11-02 1358/week @ 2020-11-09 1853/week @ 2020-11-16 1181/week @ 2020-11-23

952 downloads per month
Used in 3 crates (via pear_codegen)

MIT/Apache

24KB
397 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.9"
  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.9", default-features = false }

The compiler always colors diagnostics on nightly.

License

Licensed under either of the following, at your option:

Dependencies

~0.4–0.9MB
~21K SLoC