Did you think Macros 1.1 was only for custom derives? Think again.
Note: Requires stable Rust 1.15 or beta Rust 1.16. This library is currently affected by a regression in rustc, rust-lang/rust#39889, and does not work on the most recent nightlies. It works on stable and beta but not nightly. How times have changed, huh? A fix has been merged in rust-lang/rust#39419 and should be in the next nightly after March 1.
Two crates are required to define a macro.
This crate is allowed to contain other public things if you need, for example traits or functions or ordinary macros.
https://github.com/dtolnay/proc-macro-hack/tree/master/demo-hack
```rust
extern crate procmacrohack;
extern crate demohackimpl; pub use demohackimpl::*;
/// Add one to an expression. procmacroexprdecl!(addone! => addoneimpl);
/// A function that always returns 2. procmacroitemdecl!(twofn! => twofnimpl); ```
This crate must contain nothing but procedural macros. Private helper functions and private modules are fine but nothing can be public.
https://github.com/dtolnay/proc-macro-hack/tree/master/demo-hack-impl
```rust
extern crate procmacrohack;
procmacroexprimpl! { /// Add one to an expression. pub fn addone_impl(input: &str) -> String { format!("1 + {}", input) } }
procmacroitemimpl! { /// A function that always returns 2. pub fn twofn_impl(input: &str) -> String { format!("fn {}() -> u8 {{ 2 }}", input) } } ```
Both crates depend on proc-macro-hack
:
toml
[dependencies]
proc-macro-hack = "0.3"
Additionally, your implementation crate (but not your declaration crate) is a proc macro:
toml
[lib]
proc-macro = true
Users of your crate depend on your declaration crate (not your implementation crate), then use your procedural macros as though it were magic. They even get reasonable error messages if your procedural macro panics.
https://github.com/dtolnay/proc-macro-hack/tree/master/example
```rust
extern crate demo_hack;
two_fn!(two);
fn main() { let x = two(); let nine = addone!(x) + addone!(2 + 3); println!("nine = {}", nine); } ```
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this hack by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.