Strictly speaking this is an upstream tree-sitter bug, but I'd like to raise awareness of this since a) it might be possible to work around this by changing the grammar, and b) if it's not addressed one way or another, this parser will become unusable sooner or later (e.g., with the next ABI bump). Maybe someone more familiar with the grammar can bisect the offending rule (I tried and failed). In case it helps, here's the debug log for tree-sitter generate --no-bindings:
Trying to generate the parser with a recent
tree-sitter
CLI (including the latest 0.22.6) will trigger a panic:Strictly speaking this is an upstream tree-sitter bug, but I'd like to raise awareness of this since a) it might be possible to work around this by changing the grammar, and b) if it's not addressed one way or another, this parser will become unusable sooner or later (e.g., with the next ABI bump). Maybe someone more familiar with the grammar can bisect the offending rule (I tried and failed). In case it helps, here's the debug log for
tree-sitter generate --no-bindings
:output.log