James Coglan

@sidhant92 I'm not sure I understand what you're asking for, or what you're trying to do with your grammar. Could you give an example of the grammar you're writing and...

Can I close this issue or did you have further information about it?

Could you give an example of a grammar and input text that triggers the bug you're fixing?

I don't see a reason on paper why this couldn't happen, the main challenge is deciding which bits of state to expose to such functions, and how they transfer state...

I think this shares some of the problems of #7 in that parsing expressions do not have names. A grammar binds rule names to parsing expressions, which are arbitrarily nested,...

As mentioned in https://github.com/jcoglan/canopy/issues/7#issuecomment-1084458260 I've added a limited form of rule name capture in order to improve error messages. I am still not sold on adding rule names to parse...

No, that's exactly how you're supposed to do this. Spaced aren't special, they need including in rules just as you would any other kind of character.

Placing the `@` operator on rule _names_ would not make sense in general. It is currently supported as an annotation to expressions appearing within a _sequence_, where it causes the...

In general, Canopy assumes that all parsing expressions return a value if they match the input. An expression that doesn't match produces the special internal value `FAILURE`, and any other...

This is a deliberate design decision. The definition of what is valid syntax is assumed to lie entirely in the grammar definition, and action functions are only responsible for building...