Jan Dolinár

@ccleve Oh, I see. My bad, I guess I wasn't paying enough attention when I read the issue :roll_eyes:

It is not very fair to compare the result of generic, multi-purpose packrat parser-generator to hand-written, single-purpose parser, that is optimized by some of the worlds best developers over last...

> Also it might be a good idea to add a way of telling ackcc "Hey this string literal should be matched case-insensitively" because I don't like generating thousands of...

I have just quickly tested the imports. It's very intuitive and seems to work very well. If I understand correctly, there is slight difference in the behavior: Unused rules in...

Hi @arithy, I should have closed this PR a long time ago, but I have totally forgot about it. It is a good idea to keep the functionalities (code generation...

I have stumbled on similar behavior just this week. I don't have the original file for which it happened, but it turns out it is really simple to generate file...

I don't think it is a problem related to lookahead... The `a[777].foo` correctly matches `FunctionCall` rule, but it doesn't match `Indexing`. That is partially because `Indexing` tries to first match...

Having 150k timeseries per application (as mentioned in the linked issue) is definitely well outside of the best practices for prometheus. See for example the warning given [here](https://prometheus.io/docs/practices/naming/#labels). Using URL,...

I have tested with the new code, issue is solved. Thank you.