Lucas Bremgartner

Thanks for the well written bug report. The line in parser.go you are pointing to (https://github.com/open-policy-agent/opa/blob/master/ast/parser.go#L4362) is after the parsing of the input has finished and is building a map...

@d4l3k I not yet understand, what particular functionality your are looking for. How is the tree you are requesting different (or related) to the output you get, if the `Debug`...

OK, I understand. What would be needed for this? * Introduce a new option for the parser to instruct it to output the matched rules / syntax tree, maybe allow...

Not sure, how we could detect this in a reliable way. @cch123 if you have an idea, feel free to share.

Additionally to the updated documentation in `doc.go`, a warning could be raised by pigeon if a grammar with global state is used with memoization enabled or the memoization feature could...

This is by design. Pigeon does not care about the Go code in the PEG file but only about the PEG grammar. Go does not know anything about PEG and...

That being said, Go does not have a preprocessor so there are no preporcessor lines that could point back to the original source file.

@kpixley Thanks for the hint on the //line compiler directive. I did not know about this. I started to look into adding this to pigeon. It is possible, but there...

@F4ncyMooN Thanks for your feature request. At the moment I feel like all the necessary possibilities to achieve your goal are already present in pigeon grammar. Have you read the...

@F4ncyMooN I am currently on vacation. I will have a look when I am back.