Niko Matsakis
Niko Matsakis
I updated the title to remove the reference to Yacc but keep the part I think is good. :) Specifically I have in mind something like this (though now that...
I was considering something like this, where we use an `else` groups to separate the precedence ranks, but it doesn't permit specifying associations: ``` rust Expr: Expr = if {...
@nixpulvis it will **not** work across productions, that's the whole idea. Those kinds of scenarios are intended to be solved with conditional macros, like so: ``` rust assign -> id...
I haven't really finished documenting those yet though.
(Although I guess that this would not reduce the way you want it the way I wrote it.)
@nixpulvis just as a general piece of plumbing?
@nixpulvis I don't want to change the LR algorithm for this, I wanted to desugar it in the front-end.
(which I could totally walk you through)
This fits better with LALRPOP's overall architecture, which aims to: 1. desugar the input (`grammar::parse_tree`) to a very simple, clean model (`grammar::repr`) 2. implement the back-end algorithms in as simple...
@nixpulvis yes, it would be done as part of [`normalize::macro_expand`](https://github.com/nikomatsakis/lalrpop/tree/master/lalrpop/src/normalize/macro_expand), or possibly a new module that runs directly thereafter in `normalize::lower_helper`. It's a bit different from macro expansion, in that...