Erez Shinan

Hello @Conchylicultor , Can you please check if this PR fixes your issue? https://github.com/lark-parser/lark/pull/1451

To your question - > Why did the resolution order changed ? Hard to say, but I imagine it probably happened between 0.12.x and 1.0.0 We made a lot of...

Hi @MaxOstrowski , What arguments are you giving to Lark? Specifically as the "ambiguity" parameter?

Thank you for reporting this bug. Looks like the issue is caused by a bugfix I included in v1.2.1. I just created a PR with a fix: https://github.com/lark-parser/lark/pull/1444 If you...

Okay, new version released - https://github.com/lark-parser/lark/releases/tag/1.2.2 It should be now fixed. Let me know otherwise. Sorry for the inconvenience!

Actually I will re-open. Perhaps your problem isn't entirely solved. P.S. regarding the efficiency concerns - Earley must be aware of all the ambiguities in order to parse the text...

@v-ramesh I only abandoned it for lack of public interest. If someone wants to take this PR and re-submit it with some tests, they are welcome to do it!

I'm glad to hear you find Lark to be useful, and especially as a teaching device! Producing counter-examples for shift/reduce conflicts would be a great feature in Lark. But I...

P.S. looks like this is happening because of empty rules. For example this is working correctly: ```python grammar1 =""" start: (/b/ a?)* a: /a/ """ grammar2 =""" start: (/b/ /a/?)*...

> All of the derivations are distinct I just checked, and the second example returns two derivations instead of four, now that we added caching of the nodes. That's progress...