Erez Shinan

@marsninja Why not just run black after the standalone has been generated?

@marsninja Please address the concerns of the maintainers, or I will close this PR. Thanks.

This isn't a problem with brackets. It might be an issue with ambiguous repetition. Note that this grammar produces the same result: ```lark program: instruction* instruction: pneumonic parameter* pneumonic: CNAME...

@MegaIng I tried disabling ChildFilterLALR and the ForestToParseTree cache, as that issue suggests, but this artifact still persists.

Yes. See this example: https://github.com/lark-parser/lark/blob/master/examples/advanced/custom_lexer.py

Hi @nicktimko , thanks for letting me know! I don't know what went wrong, but I restarted the machine and it works now. Either way, if you still want to...

Have you tried [`merge_transformers()`](https://lark-parser.readthedocs.io/en/latest/visitors.html#merge-transformers) for solving this use-case? Read through this: https://github.com/lark-parser/lark/tree/master/examples/composition

I agree, a custom lookahead, aka LALR(k), would be a really nice feature. And a very difficult one to implement correctly.

I have a few questions. Why do you need to hold 3k different parsers in memory at the same time? Are the parsers all kept in their initial state, or...

Serializing / pickling Earley shouldn't be too hard. Essentially, Earley accepts only a few params, and does very little processing on them. So, if you serialize these params, you can...