Skip to content

Commit dbc3ebe

Browse files
committed
Make some editorial tweaks
1 parent 469da7b commit dbc3ebe

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/rust-2024/macro-fragment-specifiers.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ More information may be found in the tracking issue at <https://github.com/rust-
66
## Summary
77

88
- The `expr` [fragment specifier] now also supports `const` and `_` expressions.
9-
- The `expr_2021` fragment specifier has been added for backwards compatibility.
9+
- The `expr_2021` fragment specifier has been added for backwards compatibility.
1010

1111
[fragment specifier]: ../../reference/macros-by-example.html#metavariables
1212

1313
## Details
1414

15-
As new syntax is added to Rust, existing `macro_rules` fragment specifiers are sometimes not allowed to match on the new syntax in order to retain backwards compatibility. Supporting the new syntax in the old fragment specifiers is sometimes deferred until the next Edition, which provides an opportunity to update them.
15+
As new syntax is added to Rust, existing `macro_rules` fragment specifiers are sometimes not allowed to match on the new syntax in order to retain backwards compatibility. Supporting the new syntax in the old fragment specifiers is sometimes deferred until the next edition, which provides an opportunity to update them.
1616

1717
Indeed this happened with [`const` expressions] added in 1.79 and [`_` expressions] added in 1.59. In the 2021 Edition and earlier, the `expr` fragment specifier does *not* match those expressions. This is because you may have a scenario like:
1818

0 commit comments

Comments
 (0)