From c6fed1ee399d5f3dbe78a9aa808c88ff703f101f Mon Sep 17 00:00:00 2001 From: Tbkhi Date: Mon, 11 Mar 2024 09:18:44 -0300 Subject: [PATCH] Update macro-expansion.md --- src/macro-expansion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/macro-expansion.md b/src/macro-expansion.md index 0bc83d93..81ebdcc3 100644 --- a/src/macro-expansion.md +++ b/src/macro-expansion.md @@ -561,7 +561,7 @@ pattern for matching a `macro` definition as `$( $lhs:tt => $rhs:tt );+`. In other words, a `macro_rules` definition should have in its body at least one occurrence of a token tree followed by `=>` followed by another token tree. When the compiler comes to a `macro_rules` definition, it uses this pattern to -match the two token trees per rule in the definition of the `macro`, _thereby +match the two token trees per the rules of the definition of the `macro`, _thereby utilizing the `macro` parser itself_. In our example definition, the metavariable `$lhs` would match the patterns of both arms: `(print $mvar:ident)` and `(print twice $mvar:ident)`. And `$rhs` would match the