Lines Matching full:macro

4 …b-dtolnay/proc--macro--hack-8da0cb?style=for-the-badge&labelColor=555555&logo=github" height="20">…
5 …elds.io/crates/v/proc-macro-hack.svg?style=for-the-badge&color=fc8d62&logo=rust" height="20">](htt…
6 …macro--hack-66c2a5?style=for-the-badge&labelColor=555555&logoColor=white&logo=data:image/svg+xml;b…
7 …/workflow/status/dtolnay/proc-macro-hack/CI/master?style=for-the-badge" height="20">](https://gith…
19 This crate implements an alternative type of procedural macro that can be
26 Two crates are required to define a procedural macro.
36 supported procedural macro, use proc-macro-hack's #\[proc_macro_hack\]
37 attribute to define a procedural macro that works in expression position.
64 procedural macro from the implementation crate. The re-export also carries a
77 Both crates depend on `proc-macro-hack`:
81 proc-macro-hack = "0.5"
85 a proc macro crate:
89 proc-macro = true
109 [demo-hack-impl]: https://github.com/dtolnay/proc-macro-hack/tree/master/demo-hack-impl
110 [demo-hack]: https://github.com/dtolnay/proc-macro-hack/tree/master/demo-hack
111 [example]: https://github.com/dtolnay/proc-macro-hack/tree/master/example
119   proc-macro-hack macro invocation cannot contain recursive calls to the same
120   proc-macro-hack macro nor calls to any other proc-macro-hack macros. Use
121   [`proc-macro-nested`] if you require support for nested invocations.
124   local variables other than those passed by name somewhere in the macro input.
125   If your macro must refer to *local* variables that don't get named in the
126   macro input, use `#[proc_macro_hack(fake_call_site)]` on the re-export in your
130   position, proc-macro-hack does not automatically use that support, since the
132   compiling your macro to native `#[proc_macro]` on sufficiently new compilers,
136 [#10]: https://github.com/dtolnay/proc-macro-hack/issues/10
137 [#20]: https://github.com/dtolnay/proc-macro-hack/issues/20
138 [`proc-macro-nested`]: https://docs.rs/proc-macro-nested