From 87f527b36e1e7195337b596e838a2e5d5cac88a8 Mon Sep 17 00:00:00 2001 From: Daniel Henry-Mantilla Date: Tue, 15 Nov 2022 12:32:20 +0100 Subject: [PATCH 1/2] Add an anchor to the "forwarding macro fragments" paragraph Since this is a subtle idiosyncracy into which macro users sometimes bump, it can be incredibly help ful to give them a pin-pointed link to the exact paragraph talking about this. Hence the idea of adding some kind of header, and thus an anchor, to it. Since it's just a paragraph, I've gone for a very low header, such as h4. cc @nilstrieb --- src/macros-by-example.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/macros-by-example.md b/src/macros-by-example.md index 2c49300cd..861779156 100644 --- a/src/macros-by-example.md +++ b/src/macros-by-example.md @@ -76,6 +76,8 @@ delimiters for the matcher will match any pair of delimiters. Thus, for instance, the matcher `(())` will match `{()}` but not `{{}}`. The character `$` cannot be matched or transcribed literally. +#### Forwarding a matched fragment + When forwarding a matched fragment to another macro-by-example, matchers in the second macro will see an opaque AST of the fragment type. The second macro can't use literal tokens to match the fragments in the matcher, only a From 04f289ad17a9b86f9cde026d046072a5b3827486 Mon Sep 17 00:00:00 2001 From: Daniel Henry-Mantilla Date: Tue, 15 Nov 2022 21:25:08 +0100 Subject: [PATCH 2/2] Fix header hierarchy Co-authored-by: Eric Huss --- src/macros-by-example.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/macros-by-example.md b/src/macros-by-example.md index 861779156..cd9dc3402 100644 --- a/src/macros-by-example.md +++ b/src/macros-by-example.md @@ -76,7 +76,7 @@ delimiters for the matcher will match any pair of delimiters. Thus, for instance, the matcher `(())` will match `{()}` but not `{{}}`. The character `$` cannot be matched or transcribed literally. -#### Forwarding a matched fragment +### Forwarding a matched fragment When forwarding a matched fragment to another macro-by-example, matchers in the second macro will see an opaque AST of the fragment type. The second macro