- Track an anchor at the start of each Pratt subexpression and report errors from that anchor through the offending token, instead of highlighting only the final token.
- Apply this to assignment/index/place errors, prefix operators, unclosed parentheses and brackets, and related Pratt paths. Keep narrow spans for non-associative operators (e.g. chained = ).
- Add unit tests that assert the highlighted source snippets for common parse failures.
Closes: #42
Co-authored-by: Sylvestre Ledru <sylvestre@debian.org>