pom
PEG parser combinators using operator overloading without macros. (by J-F-Liu)
rust-peg
Parsing Expression Grammar (PEG) parser generator for Rust (by kevinmehall)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pom
Posts with mentions or reviews of pom.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-19.
-
Domain Specific Language embedded in Rust
pom
-
Analogues of nom crate.
Maybe a parser combinator library is not what you want? One alternative might be writing an expression parser without a library at all: https://matklad.github.io/2020/04/13/simple-but-powerful-pratt-parsing.html (Depending on the grammar you are parsing a Pratt parser might actually be a good fit!) A PEG might also be more suitable for your use case, like pom.
- Explanations and Examples for pom
-
Chumsky, a parser combinator crate that makes writing error-tolerant parsers with recovery easy and fun!
I saw the performance comparison against pom, pom is unfortunately quite slow compared to an handwritten parser as it boxes most (all?) parsers so you may want to compare against a handwritten parser, or at least something in the same ballpark (for reference, combine's json benchmark on the same data is about 6x faster with "good errors", when optimized to work on &str-like input it is about 12x faster, nom or a hand written parser may be another 10-20% faster than that, if I remember correctly.) From a brief skim of the code, I don't see anything that would hinder it from at least closing that gap however.
-
Whats the best parser generator for rust?
Everyone on this sub seems to be using nom. In my experience I find pom to be intuitive and have to write less code. Maybe it's just me I'm having a hard time understanding nom which has a lot of function calls rather than less.If you compare both the json examples on both projects, the pom example is a lot clearer to read and a lot shorter.
rust-peg
Posts with mentions or reviews of rust-peg.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-06.
-
nom > regex
And some related parser tools: - https://github.com/kevinmehall/rust-peg - https://github.com/pest-parser/pest - https://github.com/lalrpop/lalrpop
-
Letlang — Roadblocks and how to overcome them - My programming language targeting Rust
Rust is a very nice langage for implementing compilers, and has a nice ecosystem for it (logos, rust-peg, lalrpop, astmaker -- this one is mine --, etc...).
-
Is there a parsing library (lexer?) which can handle generic tokens?
My peg crate is a parser generator that supports arbitrary token types as input. See https://github.com/kevinmehall/rust-peg/blob/master/tests/run-pass/tokens.rs for an example.
-
Hey Rustaceans! Got a question? Ask here! (51/2022)!
The one rust parser-generator I used is PEG
-
Hey Rustaceans! Got a question? Ask here! (29/2022)!
The two parser generators that I am aware of are lalrpop and PEG. There both great, and have seen some use by languages that have been written in Rust.
-
Domain Specific Language embedded in Rust
rust-peg
- One Letter Programming Languages
-
Using Nom - a parser combinator library
I wanted to create a parser for Apertium Stream. In 2014, I used Whittle in Ruby. If this year were 2001, I would use Lex/Yacc. Anyway, this year is 2021. I wanted to create this parser in Rust. I tried to find what is similar to Lex/Yacc. I found Rust-Peg. I found a link to Nom from Rust-Peg's document. My first impression was Nom example is easy to read. At least, its document claimed Nom is fast.
-
Hey Rustaceans! Got an easy question? Ask here (5/2021)!
The peg crate has a resolved issue about this.
-
Rust is the second most used language for Advent of Code, after Python
I don't really know that much about parsing and grammars, other than what I've learned about regular languages and expressions and context-free languages in a standard Theory of Comp course from my university. I basically just learned peg by reading the Wikipedia article on PEGs, reading the crate documentation to understand the syntax, and then looking at some of the peg examples on their GitHub to understand how it works in practice.
What are some alternatives?
When comparing pom and rust-peg you can also consider the following projects:
nom - Rust parser combinator framework
pest - The Elegant Parser
combine - A parser combinator library for Rust
lalrpop - LR(1) parser generator for Rust
git-journal - The Git Commit Message and Changelog Generation Framework :book:
chomp - A fast monadic-style parser combinator designed to work on stable Rust.
rust-bison-skeleton - Bison frontend for Rust
chumsky - Write expressive, high-performance parsers with ease.
oak - A typed parser generator embedded in Rust code for Parsing Expression Grammars