We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
2 parents a05dd93 + a333e01 commit fec4f19Copy full SHA for fec4f19
src/doc/guide-macros.md
@@ -195,7 +195,7 @@ early_return!(input_2, [T::SpecialB]);
195
As the above example demonstrates, `$(...)*` is also valid on the right-hand
196
side of a macro definition. The behavior of `*` in transcription,
197
especially in cases where multiple `*`s are nested, and multiple different
198
-names are involved, can seem somewhat magical and intuitive at first. The
+names are involved, can seem somewhat magical and unintuitive at first. The
199
system that interprets them is called "Macro By Example". The two rules to
200
keep in mind are (1) the behavior of `$(...)*` is to walk through one "layer"
201
of repetitions for all of the `$name`s it contains in lockstep, and (2) each
0 commit comments