> It's not actually implemented as a scannerless parser, but the grammar API mostly abstracts away the parser/lexer distinction.
Any aspects of the 'not' part of 'mostly' which one should bear in mind?
Any aspects of the 'not' part of 'mostly' which one should bear in mind?
In most cases, you don't have to think about it; the obvious way to write something is the right way. There are cases where its helpful to have a mental model of how lexing works.
Nifty. So explicit GLR forks at rule level (`conflicts:`), non-forking token "conflict" resolution[1], no token regex backtracking pressure across tokens, and token resolution at a single code position can(?) differ across conflicting rules? I'm uncertain on that last bit.
> In most cases, you don't have to think about it
Well yes, but, some of us crave much more syntactically flexible languages. :)
[1] https://tree-sitter.github.io/tree-sitter/creating-parsers#c...