| Crates.io | arborium-go |
| lib.rs | arborium-go |
| version | 2.12.4 |
| created_at | 2025-12-04 22:16:17.312184+00 |
| updated_at | 2026-01-18 11:09:04.170715+00 |
| description | Go grammar for arborium (tree-sitter bindings) |
| homepage | https://github.com/bearcove/arborium |
| repository | https://github.com/bearcove/arborium |
| max_upload_size | |
| id | 1967163 |
| size | 1,871,976 |
Go grammar for tree-sitter.
Statically typed compiled language from Google; the canonical language specification.
| Inventor | Robert Griesemer, Rob Pike, Ken Thompson |
| Year | 2009 |
use arborium_go::language;
use tree_sitter_patched_arborium::Parser;
let mut parser = Parser::new();
parser.set_language(&language()).expect("Error loading go grammar");
let source_code = "/* your go code here */";
let tree = parser.parse(source_code, None).unwrap();
println!("{}", tree.root_node().to_sexp());
For most use cases, prefer the main arborium crate:
[dependencies]
arborium = { version = "*", features = ["go"] }
Or use this crate directly:
[dependencies]
arborium-go = "*"
This crate is part of Arborium, a collection of tree-sitter grammars packaged as Rust crates, maintained by Amos Wenger.
This crate packages a parser.c file generated by the tree-sitter CLI. It exports a language() function returning the tree-sitter Language for go.
Why separate crates? Tree-sitter parsers can be large (some exceed 1MB of generated C). Splitting languages into separate crates means you only compile what you need, and parallel/incremental builds are more effective.
cc cratewasm32-unknown-unknown (with custom sysroot)| Repository | tree-sitter/tree-sitter-go |
| Commit | 2346a3ab1bb3857b48b29d779a1ef9799a248cd7 |
| License | MIT |
To regenerate after upstream updates:
cargo xtask gen --name go
Found a grammar bug? Please report it to the upstream repository.
This crate uses unsafe for FFI bindings to the tree-sitter C library. The unsafe surface is minimal and limited to what tree-sitter requires. The generated parser code is produced by tree-sitter's own code generator.
Crate versions track Arborium releases, not upstream grammar versions. The upstream commit is recorded above. A major version bump occurs when grammar changes affect node names or structure (breaking for query consumers).
parser.c): MIT (from upstream grammar)