Inline Nodes generate different ids

Lezer
1

With grammar like:


BinaryExpression {
  expression !exp ArithOp { "^" } expression |
  expression !mult ArithOp { "*" | "/" | "%" } expression |
  expression !add ArithOp { "+" | "-" } expression |
}

The nodes returned for the operator will actually have different IDs (2, 3, 4), but parser.terms will only return the last ID (4). This makes matching on type.id behave differently from matching on type.name.

Is this expected?

2

Yes, multiple terms can share a name. The parser needs to distinguish between them during parsing. If you need different names, assign different node names to the rules.

I can see how the value in parser.terms is confusing. I would have actually expected the tool to not generate a term binding at all for a parameterized rule. I’ll take a look at what’s happening later.

3

Yes, this was a bug in lezer-generator — it should only emit term bindings for top-level unique (non-inline, non-parameterized) rules, but it was accidentally doing it anyway for inline rules. This patch should fix that.

1 Like
4

It might be a good idea to document this, for folks (like me) who otherwise use the terms for matching or other purposes. I’d advise them to match by name in this case.