MegaIng

If the catchall is `/.+/`, this would still happen, just starting at the first error. And using `/./` with a low priority should work for the earley parser. I don't...

> I hope one day we'll integrate a stable scan function into Lark, and then maybe it's worth revisiting this issue. Currently working on it (after finishing a review of...

You currently still have an outstanding "Request Changing" review that I think Ross thinks is fully resolved. If you have changes other than the latest I suggested, you can already...

Btw, can we drop support for the now completely unsupported versions 3.6 and 3.7? https://devguide.python.org/versions/ The `regex` stubs in typshed now uses the `/` positional only syntax, meaning `mypy` error...

> There is one design idea that I have, I hope you'll keep an open mind. If we change the definition of text to text: str | TextSlice, where TextSlice...

Specifically the think I had in mind is some kind of externally generated token stream with a custom lexer.

Imagine using something like stdlib's `tokenizer` to produce a list of tokens, and using those as the input to `Lark.parse` instead of the raw text. Or using a bytecode stream...

I am going to bed for now, but an observation I am already making is that using `TextSlice` instead requires touching a lot more code. We have quite a few...

Sorry, no, not next-few-days-soon. Forgot about this. It was a bit more work than I thought (since it also needed to touch a chunk of earley code). I am not...

If you want to work on something, maybe you can come up with a solution of the issue of multi-path imports, as seen in [this SO question](https://stackoverflow.com/questions/78692900/unclear-reason-for-terminal-collision)? The problem is...