Descriptions need not to duplicate existing guides and merely serve as a simple starting point, just so people know what Tree-sitter is capable of. Note, that they also have to accent on using compiler's API as much as possible and only resort to Tree-sitter in cases where it's not possible (such as when the tool is not written in JavaScript/TypeScript).
novusnota
commented
3 months ago
Additionally, Go bindings (and, maybe, some others) may require some updates — for that, tree-sitter-tact may have to get submitted in the community bindings repositories, like smacker/go-tree-sitter. See example of bindings here: https://github.com/smacker/go-tree-sitter/pull/58
Descriptions need not to duplicate existing guides and merely serve as a simple starting point, just so people know what Tree-sitter is capable of. Note, that they also have to accent on using compiler's API as much as possible and only resort to Tree-sitter in cases where it's not possible (such as when the tool is not written in JavaScript/TypeScript).
Depends on #12.