diff options
author | David Tolnay <dtolnay@gmail.com> | 2019-08-10 13:51:53 -0700 |
---|---|---|
committer | David Tolnay <dtolnay@gmail.com> | 2019-08-10 13:51:53 -0700 |
commit | 5dd3812c1cc01847f8e525fa3adbc6179126b5cf (patch) | |
tree | 7c68d23b48bf138647ad8b01723bab6a9798d952 | |
parent | 5218552d94bf0bd675939a6e5f87408d23533657 (diff) | |
download | platform_external_rust_crates_quote-5dd3812c1cc01847f8e525fa3adbc6179126b5cf.tar.gz platform_external_rust_crates_quote-5dd3812c1cc01847f8e525fa3adbc6179126b5cf.tar.bz2 platform_external_rust_crates_quote-5dd3812c1cc01847f8e525fa3adbc6179126b5cf.zip |
Remove outdated doc about def_site
-rw-r--r-- | src/lib.rs | 6 |
1 files changed, 1 insertions, 5 deletions
@@ -429,11 +429,7 @@ macro_rules! quote { /// /// In this example it is important for the where-clause to be spanned with the /// line/column information of the user's input type so that error messages are -/// placed appropriately by the compiler. But it is also incredibly important -/// that `Sync` resolves at the macro definition site and not the macro call -/// site. If we resolve `Sync` at the same span that the user's type is going to -/// be resolved, then they could bypass our check by defining their own trait -/// named `Sync` that is implemented for their type. +/// placed appropriately by the compiler. #[macro_export] macro_rules! quote_spanned { ($span:expr=> $($tt:tt)*) => {{ |