Nondeterministic generation of Rust code about grmtools HOT 2 CLOSED

Oh, I see, the recovery is nondeterministic. And yes, I wanted the lexing error to turn into a parsing error. I'll close this and change my code.

from grmtools.

At the moment I'm fairly sure the token IDs are deterministic, though that's not guaranteed and not really intended (you can see the relevant code here).

I think what you're seeing in your example is something different: error recovery is nondeterministically doing Insert NUM or Insert UNKNOWN_TOKEN. That nondeterminism is inevitable (see Section 5.3).

I wonder if with UNKNOWN_TOKEN you intended to turn lexing errors into parsing errors?

from grmtools.