8 releases

Uses old Rust 2015

0.1.7 Jan 13, 2021
0.1.6 Jun 14, 2020
0.1.4 Mar 17, 2020
0.1.3 Mar 6, 2019
0.1.1 Nov 21, 2018

#275 in Procedural macros

Download history 179905/week @ 2020-10-02 180588/week @ 2020-10-09 183546/week @ 2020-10-16 184930/week @ 2020-10-23 183485/week @ 2020-10-30 179909/week @ 2020-11-06 183250/week @ 2020-11-13 183412/week @ 2020-11-20 180884/week @ 2020-11-27 189952/week @ 2020-12-04 187657/week @ 2020-12-11 157785/week @ 2020-12-18 126506/week @ 2020-12-25 176249/week @ 2021-01-01 225670/week @ 2021-01-08 205843/week @ 2021-01-15

766,087 downloads per month
Used in 255 crates (11 directly)

MIT/Apache

7KB
58 lines


lib.rs:

Support for nested invocations of proc-macro-hack expression macros.

By default, macros defined through proc-macro-hack do not support nested invocations, i.e. the code emitted by a proc-macro-hack macro invocation cannot contain recursive calls to the same proc-macro-hack macro nor calls to any other proc-macro-hack macros.

This crate provides opt-in support for such nested invocations.

To make a macro callable recursively, add a dependency on this crate from your declaration crate and update the #[proc_macro_hack] re-export as follows.

// Before
# const IGNORE: &str = stringify! {
#[proc_macro_hack]
pub use demo_hack_impl::add_one;
# };
// After
# const IGNORE: &str = stringify! {
#[proc_macro_hack(support_nested)]
pub use demo_hack_impl::add_one;
# };

No change is required within your definition crate, only to the re-export in the declaration crate.

Limitations

  • Nested invocations are preprocessed by a TT-muncher, so the caller's crate will be required to contain #![recursion_limit = "..."] if there are lengthy macro invocations.

  • Only up to 64 nested invocations are supported.

No runtime deps