Crates.io | lalrpop |
lib.rs | lalrpop |
version | |
source | src |
created_at | 2015-07-26 11:48:49.391461+00 |
updated_at | 2025-01-21 19:47:45.551472+00 |
description | convenient LR(1) parser generator |
homepage | |
repository | https://github.com/lalrpop/lalrpop |
max_upload_size | |
id | 2682 |
Cargo.toml error: | TOML parse error at line 20, column 1 | 20 | 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 |
LALRPOP is a Rust parser generator framework with usability as its primary goal. You should be able to write compact, DRY, readable grammars. To this end, LALRPOP offers a number of nifty features:
Id*
and define
things like Comma<Id>
for a comma-separated list of identifiers.Expr<"all">
to represent the full range of expressions, but
Expr<"if">
to represent the subset of expressions that can appear
in an if
expression.*
and ?
.Despite its name, LALRPOP in fact uses LR(1) by default (though you can opt for LALR(1)), and really I hope to eventually move to something general that can handle all CFGs (like GLL, GLR, LL(*), etc).
The LALRPOP book covers all things LALRPOP -- or at least it intends to! Here are some tips:
Cargo.toml
.You really should read CONTRIBUTING.md
if you intend to change LALRPOP's own grammar.