megaparsec
Industrial-strength monadic parser combinator library (by mrkkrp)
nom
Rust parser combinator framework (by rust-bakery)
| megaparsec | nom | |
|---|---|---|
| 3 | 85 | |
| 892 | 9,098 | |
| - | 1.0% | |
| 6.4 | 7.4 | |
| 12 days ago | 15 days ago | |
| Haskell | Rust | |
| BSD 2-clause "Simplified" License | MIT License |
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.
megaparsec
Posts with mentions or reviews of megaparsec.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-23.
-
An apologia for lazy evaluation
Did you use megaparsec between August 2018 and August 2022? If so, you had a space leak. Granted, maybe it was small enough that it wasn't "an issue", but it just goes to show that it's so easy to introduce space leaks in Haskell that experts do it regularly.
-
is there an interpreter/compiler i can just put in a folder and use?
- Haskell's megaparsec library
-
Failing to parse Elixir with Megaparsec
Last year I spent some time trying to parse Elixir with Megaparsec.
nom
Posts with mentions or reviews of nom.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-10-28.
-
Planespotting with Rust: using nom to parse ADS-B messages
Just in case you are not familiar with nom, it is a parser combinator written in Rust. The most basic thing you can do with it is import one of its parsing functions, give it some byte or string input and then get a Result as output with the parsed value and the rest of the input or an error if the parser failed. tag for example is used to recognize literal character/byte sequences.
-
Show HN: Rust nom parsing Starcraft2 Replays into Arrow for Polars data analysis
I may be the only one not familiar, but nom refers to https://github.com/rust-bakery/nom which looks like a pretty handy way to parse binary data in Rust.
-
Is this a good way to free up some memory?
Lots of people use nom for their parsing needs, but that's not the only game in town and there other options.
-
What is the state of the art for creating domain-specific languages (DSLs) with Rust?
As much as I love nom as well as other parser combinator libraries, regex-based parsers, BNF/EBNF-based parsers, etc. I always end up going back to plain old text-based char-by-char scanners.
-
What's everyone working on this week (22/2023)?
I am using nom / nom_locate to build the parser side because I've done a handful of other projects with it, and I plan to use tower-lsp to hook up the language server side.
-
Tokenizing
Look into a parsing library such as https://github.com/rust-bakery/nom
-
Something like pydantic but for just strings?
If we were in /r/learnrust I'd have recommended the nom crate for this.
- Nom: Parser Combinators Library in Rust
-
lua bytecode parser written in rust
Thanks to the flexibility of [nom](https://github.com/rust-bakery/nom), it is very easy to write your own parser in rust, read [this article](https://github.com/metaworm/luac-parser-rs/wiki/Write-custom-luac-parser) to learn how to write a luac parser
-
Should I revisit my choice to use nom?
I've been working on an assembler and right now it uses nom. While nom isn't great for error messages, good error messages will be important for this particular assembler (current code), so I've been attempting to use the methods described by Eyal Kalderon in Error recovery with parser combinators (using nom).
What are some alternatives?
When comparing megaparsec and nom you can also consider the following projects:
parsec - A monadic parser combinator library
pest - The Elegant Parser
attoparsec - A fast Haskell library for parsing ByteStrings
lalrpop - LR(1) parser generator for Rust
attoparsec-parsec - An Attoparsec compatibility layer for Parsec
combine - A parser combinator library for Rust
trifecta - Parser combinators with highlighting, slicing, layout, literate comments, Clang-style diagnostics and the kitchen sink
pom - PEG parser combinators using operator overloading without macros.
pipes-attoparsec - Utilities to convert a parser into a pipe
rust-peg - Parsing Expression Grammar (PEG) parser generator for Rust
streaming-binary - Incremental serialization and deserialization of Haskell values.
chumsky - Write expressive, high-performance parsers with ease.