Skip to content

Commit 6ce7804

Browse files
authored
Don't use PathPattern in RangePattern bounds
The use of `PathPattern` instead of `PathExpression` in `RangePattern` is IMO confusing, since these values are not patterns and are not represented as patterns in the AST.
1 parent abd11a1 commit 6ce7804

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/patterns.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -423,7 +423,7 @@ match tuple {
423423
>    | [BYTE_LITERAL]\
424424
> &nbsp;&nbsp; | `-`<sup>?</sup> [INTEGER_LITERAL]\
425425
> &nbsp;&nbsp; | `-`<sup>?</sup> [FLOAT_LITERAL]\
426-
> &nbsp;&nbsp; | [_PathPattern_]
426+
> &nbsp;&nbsp; | [_PathExpression_]
427427
428428
Range patterns match values within the range defined by their bounds. A range pattern may be
429429
closed or half-open. A range pattern is closed if it has both a lower and an upper bound, and

0 commit comments

Comments
 (0)