commit | a2aa4d09ed0bee020bb85deae2e788b1cb3e3043 | [log] [tgz] |
---|---|---|
author | David Tolnay <dtolnay@gmail.com> | Mon Jan 08 13:23:38 2018 -0800 |
committer | GitHub <noreply@github.com> | Mon Jan 08 13:23:38 2018 -0800 |
tree | d6d2008b11f89f14bd7f1924cfdfdea0ca123ef4 | |
parent | c8f09623baa68ae120f9ab7194c617386c5e8467 [diff] | |
parent | 33eb276a63c2fd6416f0fb1e5bf8bc41d94c6be7 [diff] |
Merge pull request #59 from mystor/tt_eq_hash Implement Hash and PartialEq for quote::Tokens
This crate provides the quote!
macro for turning Rust syntax tree data structures into tokens of source code.
Procedural macros in Rust receive a stream of tokens as input, execute arbitrary Rust code to determine how to manipulate those tokens, and produce a stream of tokens to hand back to the compiler to compile into the caller's crate. Quasi-quoting is a solution to one piece of that -- producing tokens to return to the compiler.
The idea of quasi-quoting is that we write code that we treat as data. Within the quote!
macro, we can write what looks like code to our text editor or IDE. We get all the benefits of the editor's brace matching, syntax highlighting, indentation, and maybe autocompletion. But rather than compiling that as code into the current crate, we can treat it as data, pass it around, mutate it, and eventually hand it back to the compiler as tokens to compile into the macro caller's crate.
This crate is motivated by the procedural macro use case, but is a general-purpose Rust quasi-quoting library and is not specific to procedural macros.
Version requirement: Quote supports any compiler version back to Rust's very first support for procedural macros in Rust 1.15.0.
[dependencies] quote = "0.4"
#[macro_use] extern crate quote;
The quote crate provides a quote!
macro within which you can write Rust code that gets packaged into a quote::Tokens
and can be treated as data. You should think of Tokens
as representing a fragment of Rust source code. Call to_string()
on a Tokens
to get back the fragment of source code as a string, or call into()
to stream them as a TokenStream
back to the compiler in a procedural macro.
Within the quote!
macro, interpolation is done with #var
. Any type implementing the quote::ToTokens
trait can be interpolated. This includes most Rust primitive types as well as most of the syntax tree types from syn
.
let tokens = quote! { struct SerializeWith #generics #where_clause { value: &'a #field_ty, phantom: ::std::marker::PhantomData<#item_ty>, } impl #generics serde::Serialize for SerializeWith #generics #where_clause { fn serialize<S>(&self, s: &mut S) -> Result<(), S::Error> where S: serde::Serializer { #path(self.value, s) } } SerializeWith { value: #value, phantom: ::std::marker::PhantomData::<#item_ty>, } };
Repetition is done using #(...)*
or #(...),*
similar to macro_rules!
. This iterates through the elements of any variable interpolated within the repetition and inserts a copy of the repetition body for each one. The variables in an interpolation may be anything that implements IntoIterator
, including Vec
or a pre-existing iterator.
#(#var)*
— no separators#(#var),*
— the character before the asterisk is used as a separator#( struct #var; )*
— the repetition can contain other things#( #k => println!("{}", #v), )*
— even multiple interpolationsNote that there is a difference between #(#var ,)*
and #(#var),*
—the latter does not produce a trailing comma. This matches the behavior of delimiters in macro_rules!
.
Any interpolated tokens preserve the Span
information provided by their ToTokens
implementation. Tokens that originate within a quote!
invocation are spanned with Span::def_site()
.
A different span can be provided explicitly through the quote_spanned!
macro.
The quote!
macro relies on deep recursion so some large invocations may fail with "recursion limit reached" when you compile. If it fails, bump up the recursion limit by adding #![recursion_limit = "128"]
to your crate. An even higher limit may be necessary for especially large invocations. You don't need this unless the compiler tells you that you need it.
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.