pest VS parse-rosetta-rs

And some related parser tools: - https://github.com/kevinmehall/rust-peg - https://github.com/pest-parser/pest - https://github.com/lalrpop/lalrpop

I had recently completed the first year of my Computer Science class at school and will begin my second year soon. My schools' class forces the use of Java programming language, and I absolutely hated it. So, over the course of a little less than a month, I wrote my own programming language, in Rust (objectively best programming language), using pest, to be as similar to Rust as possible, but compiling to Java.

I second pest.rs. Using it is fairly intuitive and there's also a live playground on their website which is great for quickly developing and testing your AST (abstract syntax tree) parser for whatever language you're implementing.

This is where you'll run into trouble. People who write parsing-related Rust crates generally write things like pest that expect their syntax to be defined completely at compile time so the parser can be run through the compiler's optimizers for best performance.

Give https://pest.rs a try.

For now I have used pest to generate an AST that borrows from the given input. But if I can manage to make the parser generic over the return type it may be worth a refactoring.

Comparing performance of parser libraries

For a very rough comparison of parsers, see https://github.com/rosetta-rs/parse-rosetta-rs

Since this takes a unique approach, would you be interested in adding it to parse-rosetta-rs? Its a repo to help users do a comparative analysis of parser crates, providing some very crude stats to help get them started and allowing them to compare what the APIs look like.

The reason I assume its unrelated to combine is that for the json implementation, a previous version of combine built in about the same time as nom

I'm tempted to collect all of these benchmark repos into a github org to make them easier to find. So far I know of parser, md, argparse, and template languages.