From fffebaf9fab91db1102076b843075273d9646b06 Mon Sep 17 00:00:00 2001
From: Almost89 <78914413+Almost89@users.noreply.github.com>
Date: Thu, 6 Mar 2025 14:24:51 +0000
Subject: [PATCH] remove string interps as they aren't static

---
 docs/syntax-pattern-and-match-expressions.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/docs/syntax-pattern-and-match-expressions.md b/docs/syntax-pattern-and-match-expressions.md
index dd62640..7c19d2a 100644
--- a/docs/syntax-pattern-and-match-expressions.md
+++ b/docs/syntax-pattern-and-match-expressions.md
@@ -52,7 +52,7 @@ There are two main components proposed in this RFC:
 The proposed grammar changes are below:
 
 ```ebnf
-pattern = NUMBER | STRING | 'nil' | 'true' | 'false' | stringinterp | '*' | pattern 'or' pattern | '(' pattern ')' | NUMBER 'until' NUMBER | 'not' pattern
+pattern = NUMBER | STRING | 'nil' | 'true' | 'false' | '*' | pattern 'or' pattern | '(' pattern ')' | NUMBER 'until' NUMBER | 'not' pattern
 matcharm = pattern ['if' exp] '->' exp
 matcharmlist = matcharm {',' matcharm} [',']
 matchexp = 'for' exp 'match' '(' matcharmlist ')'
@@ -70,11 +70,12 @@ The main purpose of a pattern is to check if a value *matches* some definition.
 
 #### Exact
 
-The *exact* pattern matches exactly what value is given to it. A pattern is an exact if given the following:
+The *exact* pattern matches exactly what value is given to it. The following data types are valid exact patterns:
+
+- Strings
+- Numbers
+- Booleans
 
-- Strings and interpolated strings;
-- Numbers; and finally
-- Booleans.
 Anything else produces a syntax error.
 
 > Identifiers and index expressions were included in an older version of this RFC, however, they were removed as there were few valid use cases for dynamic patterns and all they do is increase complexity.