Previously, we attempted to completely separate the parse states for item sets with non-terminal extras from the parse states for other rules. But there was not a complete separation. It actually isn't necessary to separate the parse states in this way. The only special behavior for parse states with non-terminal extra rules is what happens at the *end* of the rule: these parse states need to perform an unconditional reduction. Luckily, it's possible to distinguish these *non-terminal extra ending* states from other states just based on their normal structure, with no additional state. |
||
|---|---|---|
| .. | ||
| benches | ||
| npm | ||
| src | ||
| vendor | ||
| build.rs | ||
| Cargo.toml | ||
| README.md | ||
Tree-sitter CLI
The Tree-sitter CLI allows you to develop, test, and use Tree-sitter grammars from the command line. It works on MacOS, Linux, and Windows.
Installation
You can install the tree-sitter-cli with cargo:
cargo install tree-sitter-cli
or with npm:
npm install tree-sitter-cli
You can also download a pre-built binary for your platform from the releases page.
Dependencies
The tree-sitter binary itself has no dependencies, but specific commands have dependencies that must be present at runtime:
- To generate a parser from a grammar, you must have
nodeon your PATH. - To run and test parsers, you must have a C and C++ compiler on your system.
Commands
-
generate- Thetree-sitter generatecommand will generate a Tree-sitter parser based on the grammar in the current working directory. See the documentation for more information. -
test- Thetree-sitter testcommand will run the unit tests for the Tree-sitter parser in the current working directory. See the documentation for more information. -
parse- Thetree-sitter parsecommand will parse a file (or list of file) using Tree-sitter parsers.