You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use a nested tokeniser to parse the characters within a string literal. (#96)
As per #79 I've had a go at replacing the string literal post-processor
with a nested tokeniser. I think it's simpler but YMMV.
Also I noticed along the way that we weren't processing hex literals at
all previously, nor did we test for them, obviously.
I'm `unwrap()`ing the inner tokeniser result as it should be verified by
the original `StringLiteral` regex.
There's also a problem we have with naively using ASCII strings, or
whatever, instead of proper UTF8. In particular we're allowing `\xHH`
literals which could produce invalid UTF sequences accidentally, and we
don't test against extended UTF characters at all... I'm not sure if
they'd pass. I'll create a new issue for this.
Closes#79.
Copy file name to clipboardExpand all lines: yurtc/README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ cargo run --bin yurtc -- --help
34
34
35
35
### Running Unit Tests
36
36
37
-
Unit tests can be run using `cargo run` in the `yurt/yurtc` directory. However, it is recommended that the tests are run using the [`cargo-nextest`](https://nexte.st/) package instead. To install `cargo-nextest`:
37
+
Unit tests can be run using `cargo test` in the `yurt/yurtc` directory. However, it is recommended that the tests are run using the [`cargo-nextest`](https://nexte.st/) package instead. To install `cargo-nextest`:
0 commit comments