fix: string lexing advances based on char boundaries.

instead of incrementing 1 byte at the time, advance to the next boundary. this prevents slicing into an invalid byte index.
Demonstrandum · Nov 23, 2024 · f6dc991 · f6dc991
1 parent 7fae4c9
commit f6dc991
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/Cargo.toml b/Cargo.toml
@@ -4,7 +4,7 @@ description = "Symbolic Expressions As Markup."
 keywords = ["markup", "lisp", "macro", "symbolic-expression", "sexp"]
 license-file = "LICENSE"
 homepage = "https://git.knutsen.co/seam"
-version = "0.2.7"
+version = "0.2.8"
 authors = ["Demonstrandum <samuel@knutsen.co>"]
 edition = "2021"
 

diff --git a/src/parse/lexer.rs b/src/parse/lexer.rs
@@ -242,7 +242,7 @@ impl<'a> Lexer {
                 } else {
                     reading_escape = false;
                 }
-                self.increment_byte_offsets(1);
+                let _ = self.consume_char();
             }
             let end_of_string = self.byte_offset.get();
             self.increment_byte_offsets(3);
@@ -273,7 +273,7 @@ impl<'a> Lexer {
                 } else {
                     reading_escape = false;
                 }
-                self.increment_byte_offsets(1);
+                let _ = self.consume_char();
             }
             let end_of_string = self.byte_offset.get();
             self.increment_byte_offsets(1);