ObserverOfTime
ObserverOfTime
> I'm still learning (first time using Rust after a C/C++ background). My goodness the syntax is weird... Matching case on tuples is an awesome feature though -- didn't know...
Please use the issue template.
> They can, but what for? They're defined in `parser.c`, so declaring them in `parser.h` seems correct. `parser.h` is the bread-and-butter header. I'd like to keep it minimal and identical...
> What is the linkage on these symbols? If they are not static, then they must be prefixed with ‘tree_sitter_$GRAMMAR_NAME’ to avoid name collisions. It would be nice to not...
I'm assuming the parser errors were caused by macros so I'm skipping those files.
The fields are likely related to #1865. Not sure why `"ERROR"` isn't working though.
Being able to assign field names to hidden nodes would still be nice.
Because I want nodes like escape characters to be highlightable but not show up in the tree.
Init expects user input. It cannot run non-interactively. Unless you [create `tree-sitter.json`](https://github.com/tree-sitter-grammars/template/blob/32e591467c646a53efc5e1822f609eb686a92c73/.github/workflows/setup.yml#L23-L53) beforehand.
I suppose this proves that the parser did not break due to any of the changes in #137.