squiid/rust
1
0
Fork 0
Code Issues Pull requests Projects Activity

Fix typo: intuitive -> unintuitive

Browse source
This commit is contained in:
Nicholas Bishop 2014-12-14 13:38:46 -05:00
parent 93c0610096
commit a333e013fc
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
src/doc/guide-macros.md
View file

@ -195,7 +195,7 @@ early_return!(input_2, [T::SpecialB]);
As the above example demonstrates, `$(...)*` is also valid on the right-hand As the above example demonstrates, `$(...)*` is also valid on the right-hand
side of a macro definition. The behavior of `*` in transcription, side of a macro definition. The behavior of `*` in transcription,
especially in cases where multiple `*`s are nested, and multiple different especially in cases where multiple `*`s are nested, and multiple different
names are involved, can seem somewhat magical and intuitive at first. The names are involved, can seem somewhat magical and unintuitive at first. The
system that interprets them is called "Macro By Example". The two rules to system that interprets them is called "Macro By Example". The two rules to
keep in mind are (1) the behavior of `$(...)*` is to walk through one "layer" keep in mind are (1) the behavior of `$(...)*` is to walk through one "layer"
of repetitions for all of the `$name`s it contains in lockstep, and (2) each of repetitions for all of the `$name`s it contains in lockstep, and (2) each