datalog: tokenizer raises on unexpected characters (256/256)
Some checks failed
Test, Build, and Deploy / test-build-deploy (push) Failing after 45s

Bug: characters not recognised by any branch of `scan!` (`?`,
`!`, `#`, `@`, `&`, `|`, `\\`, `^`, etc.) were silently consumed
via `(else (advance! 1) (scan!))`. Programs with typos would
parse to a stripped version of themselves with no warning —
`?(X).` became `(X).` and produced confusing downstream errors.

Fix: the else branch now raises a clear "unexpected character"
error with the offending char and its position.

1 new tokenize test.
This commit is contained in:
2026-05-10 21:17:07 +00:00
parent 69a53ece43
commit 3a1ecaa362
4 changed files with 21 additions and 7 deletions

View File

@@ -1,10 +1,10 @@
# datalog scoreboard
**255 / 255 passing** (0 failure(s)).
**256 / 256 passing** (0 failure(s)).
| Suite | Passed | Total | Status |
|-------|--------|-------|--------|
| tokenize | 29 | 29 | ok |
| tokenize | 30 | 30 | ok |
| parse | 22 | 22 | ok |
| unify | 28 | 28 | ok |
| eval | 38 | 38 | ok |