Sean Young
Sean Young
@Kixiron in the example above the &[u8] is 'static, so this does not hold any water.
That is true but how is that relevant for _this_ bug?
Stack trace: ``` #0 0x00007ffff7a8f9d5 in raise () from /lib64/libc.so.6 #1 0x00007ffff7a788a4 in abort () from /lib64/libc.so.6 #2 0x00007ffff7a78789 in __assert_fail_base.cold () from /lib64/libc.so.6 #3 0x00007ffff7a88026 in __assert_fail () from...
You are right, this looks broken.
`(statement IGNORE)*` becomes a node in tree, which is incorrectly labelled `Terminal`. I've just pushed a change which labels them `List` (amongst others). Let me know how this works for...
lrpeg does generate too many nodes. Lots of them do not have useful information. Does pest have a way of marking a rule/line as "do not generate nodes for this"...
How can the parser generator decided which nodes to create and which not to create nodes for?
We could take inspiration from pest and do not create nodes for rules which start with an underscore.
So the idea is that if a node is hidden, then it will inherit its (non-hidden) children. So `lhs` and `rhs` are in the parse tree, even though `_expr0` is...
All good stuff. Yes I know about language servers, this makes sense. I think we should store reference to the input.