Dragoș Tiselice

I do agree with you that ideally you'd get a pretty AST that you can consume, but I also don't really see this working very well when defined inside of...

IMHO, writing all those separate expression rules makes the grammar quite verbose, while adding little context. It would be fairly easy to optimize these rules with a custom optimizer, since...

No, no. I think this is a fair use case, but it's something to consider post 3.0. Also, if this was hypothetically already optimized, how would you imagine the AST...

@segeljakt, it's manual, but type-checked. This API will be called at parse time to actually generate the AST. `op` is a `Pair`, yes.

@hansihe, you should give https://pest-parser.github.com a try. It has an editor that helps. But, yes, this is something needed. By the way, if you're curious about writing an Erlang grammar...

I've tried writing a solution to this and it's a bit more involved to get a decent trace. Basically, all positive and negative rules in an `Error` have their own...

I like the idea and I think it could potentially be something to be included in 2.0 or 2.1. However, I would prefer a slightly different approach. How about every...

@Aaronepower Examples and reference are found in the `pest_derive` crate whose documentation is currently offline because of a bug in docs.rs.

@benruijl, what kind of custom errors? Error type has a custom error that you could use at semantic level. For parsing, you can have special rules, that, when they match,...

I'm not exactly sure what you're looking for. Feel free to drop a message on Gitter.