Eldred Habert
Eldred Habert
I haven't measured, no; but I do have a lot of tokens, and can generate quite a few syntax errors on a bad day. I'm thinking more that since those...
I think not. Maybe you could specifically exclude leading symbols from the offending operator branches and then handle them specially in `StringOrExpr`, but I foresee combinatorial explosion and/or a lot...
No, I mean that people would be surprised that `===` doesn't work on expressions.
We *could* make it `~=` and `!~`. But that would incorrectly lex someone writing `!~1`, e.g. `!\1` with `m ~1`.
I've attached logs to the OP. “yield” does not appear in any of them, though.
More or less relatedly, I've got LALRPOP to seemingly hang by making a grammar mistake (move [this line](https://github.com/ISSOtm/rsgbds/blob/ec52543c7daa91e84fafc5b866f6e71fccec55d5/src/asm/syntax/parser.lalrpop#L543) to the `ExprAtomNoIdent` production, e.g. on line 548) that caused it to...
I'm pretty sure the OOM stems from the amount of data being buffered, so the size of the grammar plays a role in that specific consequence, but I think it'd...
Sure, you know what, I'm game to learn about parser generators, I can try learning the state management. Let me know if you'd prefer a faster means of communication than...
What's strange is that this does not look like a RGBDS error, so something's afoot here within hUGETracker itself. I'm tempted to ask SuperDisk directly... :S
That likely means that fO does require a later version of RGBDS than hT ships. That may be a problem, I'll investigate separately. Thank you!