Erez Shinan

It should be possible in Lerche. Ambiguity is indeed the main worry here, but similar rule names are easy to solve: https://github.com/lark-parser/lark/blob/master/examples/composition/storage.lark

My impression is that most of the pre-compilation time is spent compiling the Julia code, rather than running it, and once that's accomplished, the size of the grammar doesn't matter...

Good change. But I have a feeling this might trigger some hidden bugs in various repos.

I think that you're right that your function isn't being called. That's because you defined it as `?acos_func`, and the "?" tells Lark that if there is only 1 argument,...

Well, alias (`->`) doesn't have performance costs. Using `?` does have a small cost, but I think it's very negligible.

I agree that the deepcopy is the most likely candidate / suspect. I think the deepcopy is there because the callbacks (i.e. inline transformer) might change the objects they are...

Sorry, my message was to @MegaIng . Anyway, I think we can make accepts() pretty fast if we do those things.

@Daniel63656 I created a PR that might solve your performance problems. Can you give it a try and let me know if it helped? https://github.com/lark-parser/lark/pull/1419

There could be more optimizations done, but sounds like it's good enough right now, so I'm closing the issue.

I think playing it safe is the best approach for default themes. It's better to risk something being less distinct, than it being hard to read even when your attention...