From 6ce7804bee418b3a5240047f5ad4f527f83eaa8b Mon Sep 17 00:00:00 2001
From: Florian Diebold <flodiebold@gmail.com>
Date: Thu, 5 May 2022 12:11:01 +0200
Subject: [PATCH] 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.
---
 src/patterns.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/patterns.md b/src/patterns.md
index 91b8a7f48..5c81ecd87 100644
--- a/src/patterns.md
+++ b/src/patterns.md
@@ -423,7 +423,7 @@ match tuple {
 > &nbsp;&nbsp; | [BYTE_LITERAL]\
 > &nbsp;&nbsp; | `-`<sup>?</sup> [INTEGER_LITERAL]\
 > &nbsp;&nbsp; | `-`<sup>?</sup> [FLOAT_LITERAL]\
-> &nbsp;&nbsp; | [_PathPattern_]
+> &nbsp;&nbsp; | [_PathExpression_]
 
 Range patterns match values within the range defined by their bounds. A range pattern may be
 closed or half-open. A range pattern is closed if it has both a lower and an upper bound, and