type-sitter-proc
| Crates.io | type-sitter-proc |
| lib.rs | type-sitter-proc |
| version | |
| source | src |
| created_at | 2023-05-08 12:09:56.330063 |
| updated_at | 2024-11-30 13:36:37.340696 |
| description | procedural macros for type-sitter (generate typed wrappers for tree-sitter grammars from node-types.json and queries) |
| homepage | |
| repository | https://github.com/Jakobeha/type-sitter/ |
| max_upload_size | |
| id | 859722 |
| Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
Jakob Hain (Jakobeha)
documentation
README
type-sitter-proc: generate type-sitter wrappers via procedural macros
See type-sitter for background information. This exports procedural macros which generate typed nodes. Typed nodes can also be generated from a built-script using type-sitter-gen, or from a command-line interface using type-sitter-cli.
Instead of depending on this, typically you should depend on type-sitter instead with the proc feature (enabled by default). type-sitter with the proc feature re-exports this crate, but also type-sitter-lib, which the generated code depends on at runtime.