Support inline rule about peginator HOT 5 CLOSED

Yeah, this looks like the same thing as Tatsu's "include operator": https://tatsu.readthedocs.io/en/stable/syntax.html#id29

The main goal would be to flatten the resulting structure, right?

I was thinking about implementing this feature, because I used it extensively back in the day, but by the current architecture converts rules independently from each-other, so a bunch of refactoring would be needed to do this. Or maybe a preprocessing step.

Out of curiosity, which parsing lib uses ~ for this?

from peginator.

By the way, for this specific case in peginator you could use an override rule to flatten the structure the same way by writing something like this:

assign_statement = 
     LET "(" pairs:assign_pair_list ")" [type_hint] SET assign_rhs [eos] |
     LET "(" pairs:assign_pair_list ")" [type_hint] [eos] |
     LET pairs:assign_pair_list SET assign_rhs [eos] |
     LET pairs:assign_pair_list eos ;

assign_pair_list = @:assign_pair {Comma @:assign_pair} [Comma] ;
assign_pair = {MODIFIERS} Symbol [type_hint] ;
assign_rhs = if_statement|match_statement|expr ;
LET =  "let" ;
SET =  "=" ;

But I understand this does not solve the case where there are multiple fields in the inlined rule.

from peginator.

Yes, the main purpose is to get a flat structure and reduce redundant dot calls

from peginator.

I use a preprocessing to generate peginator ast to achieve inline

Can the grammar module be set to pub?

The current implementation uses interpolated strings, which are neither sound nor type-safe.

from peginator.

Sure I can, but I'm not sure if you want to go that low level (and I guess generate code directly from the AST), it will be pretty unstable.

Note that I'm working on this feature. The syntax will be:

ComplexRule = >OtherRule { >OtherRule2 };

OtherRule = x:Number "," y:Number;
OtherRule = "(" y:Number "," z:Number ")";

It will be preprocessed to be equivalent to the following:

ComplexRule = x:Number "," y:Number { y:Number "," z:Number };

OtherRule = x:Number "," y:Number;
OtherRule = "(" y:Number "," z:Number ")";

Note how the same field names are used.
I think "Dead" rules will not be automatically eliminated from the generated code, but instead I'll just disable the dead code warning for the generated part.

from peginator.