diff options
| author | Alex Burka <durka42+github@gmail.com> | 2015-12-15 20:48:25 -0500 |
|---|---|---|
| committer | Alex Burka <durka42+github@gmail.com> | 2015-12-15 20:48:25 -0500 |
| commit | d91b256fe54b5ac2095c4417407497b0739c8b29 (patch) | |
| tree | b21bcf94f6039074d644dd1b82063b7b19f9bb78 /src | |
| parent | 9e63cecb10a3a22abed9c230c5daf268dc258bf3 (diff) | |
| download | rust-d91b256fe54b5ac2095c4417407497b0739c8b29.tar.gz rust-d91b256fe54b5ac2095c4417407497b0739c8b29.zip | |
change macro ambiguity example from ty to ident
The previous example had no chance of compiling in either form, due to the restrictive follow set for `ty`. This one has the desired behavior: http://is.gd/kYdw4g (well, I don't exactly desire this behavior at all, but it's true at least :p )
Diffstat (limited to 'src')
| -rw-r--r-- | src/doc/book/macros.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/doc/book/macros.md b/src/doc/book/macros.md index f7f27858cd2..e4a900a2b1a 100644 --- a/src/doc/book/macros.md +++ b/src/doc/book/macros.md @@ -485,10 +485,10 @@ These rules provide some flexibility for Rust’s syntax to evolve without breaking existing macros. The macro system does not deal with parse ambiguity at all. For example, the -grammar `$($t:ty)* $e:expr` will always fail to parse, because the parser would -be forced to choose between parsing `$t` and parsing `$e`. Changing the +grammar `$($i:ident)* $e:expr` will always fail to parse, because the parser would +be forced to choose between parsing `$i` and parsing `$e`. Changing the invocation syntax to put a distinctive token in front can solve the problem. In -this case, you can write `$(T $t:ty)* E $e:exp`. +this case, you can write `$(I $i:ident)* E $e:expr`. [item]: ../reference.html#items |