ThatXliner

> I just had a crazy thought. What if Lark accepted a `grammar_grammar` argument, which would describe the syntax for the grammar? (it should work as long as the structure...

+1 > Rules whose name begins with an underscore will be inlined into their containing rule My intuition says that it’s going to be done when lark constructs a parser...

In my opinion _rules and the like should be grammar level ?rules should be during/after parsing

Oh right. My bad. I was thinking about the `_templates{}`. I think those should be non-recursive for most use cases. If that may break some people’s code, why not an...

I just think that might break something… 🤷‍♂️

Like.. preprocessing? You can replace `FORWARD_SLASH` with `"/"` if you don't want it

I think you can first have a generic `fraction` rule. Then, when transforming, determine whether to change it to an `improper` or `proper` rule. Personally, I don't you should do...

`return node`, maybe

Why can't one just inline it in the grammar?

> in a way that cooperated with my conda environment I wonder if [pyenv](https://github.com/pyenv/pyenv) could help you get out of that mess 😉