From bbba872dde00b7947e75c6055dba5c82f2f7978a Mon Sep 17 00:00:00 2001 From: Tang Chenglong Date: Sat, 26 Mar 2016 23:59:16 +0800 Subject: [PATCH] docs: make some text changes on Section `Macros` (1) In contrast to `that`, `so that` expresses `result` indicated by the sentence, not `reason`; (2) `block` is an expression, and may be have an expression, so I add `optional an expression` to make more precise; (3) When I read here, I was confused with what `the child` referred to. After modification, it would be better. --- src/doc/book/macros.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/doc/book/macros.md b/src/doc/book/macros.md index 188abb316ab..1dbf8b49132 100644 --- a/src/doc/book/macros.md +++ b/src/doc/book/macros.md @@ -337,8 +337,8 @@ fn main() { } ``` -Instead you need to pass the variable name into the invocation, so it’s tagged -with the right syntax context. +Instead you need to pass the variable name into the invocation, so that it’s +tagged with the right syntax context. ```rust macro_rules! foo { @@ -470,7 +470,7 @@ which syntactic form it matches. * `ty`: a type. Examples: `i32`; `Vec<(char, String)>`; `&T`. * `pat`: a pattern. Examples: `Some(t)`; `(17, 'a')`; `_`. * `stmt`: a single statement. Example: `let x = 3`. -* `block`: a brace-delimited sequence of statements. Example: +* `block`: a brace-delimited sequence of statements and optional an expression. Example: `{ log(error, "hi"); return 12; }`. * `item`: an [item][item]. Examples: `fn foo() { }`; `struct Bar;`. * `meta`: a "meta item", as found in attributes. Example: `cfg(target_os = "windows")`. @@ -509,7 +509,7 @@ A macro defined within the body of a single `fn`, or anywhere else not at module scope, is visible only within that item. If a module has the `macro_use` attribute, its macros are also visible in its -parent module after the child’s `mod` item. If the parent also has `macro_use` +parent module after its `mod` item. If the parent also has `macro_use` then the macros will be visible in the grandparent after the parent’s `mod` item, and so forth.