lets_expect
parse-rosetta-rs
lets_expect | parse-rosetta-rs | |
---|---|---|
2 | 10 | |
59 | 77 | |
- | - | |
0.0 | 7.7 | |
about 1 year ago | 16 days ago | |
Rust | Python | |
MIT License | MIT License |
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.
lets_expect
-
Announcing lets_expect - Clean tests in Rust.
Github docs.rs
-
Testing in rust: are there any useful crates, macros etc that you use to make this easier and less verbose?
For that reason I've recently created lets_expect. It's a procedural macro that introduces its own syntax for unit tests inspired by RSpec's one-liner syntax. I think it looks very clean and concise. I consider it experimental at this point, so I haven't announced it anywhere yet, but I use it to test some of my Rust code. Basic structure is as follows:
parse-rosetta-rs
-
nom > regex
Comparing performance of parser libraries
-
Show HN: Rust nom parsing Starcraft2 Replays into Arrow for Polars data analysis
For a very rough comparison of parsers, see https://github.com/rosetta-rs/parse-rosetta-rs
-
[RELEASE] Yap 0.9: A light-weight dependency free parser combinator style library
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.
-
Announcing lets_expect - Clean tests in Rust.
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
- Practical Parsing in Rust with nom
-
GitHub - epage/parse-benchmarks-rs
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.
What are some alternatives?
jasmine - Simple JavaScript testing framework for browsers and node.js
template-benchmarks-rs - Collected benchmarks for templating crates written in Rust
rstest - Fixture-based test framework for Rust
rust_serialization_benchmark - Benchmarks for rust serialization frameworks
AssertJ - AssertJ is a library providing easy to use rich typed assertions
chumsky - Write expressive, high-performance parsers with ease.
toml - Rust TOML Parser
s2prot - Decoder/parser of Blizzard's StarCraft II replay file format (*.SC2Replay)
kani - Kani Rust Verifier
pdx-tools - View maps, graphs, and tables of your save and compete in a casual, evergreen leaderboard of EU4 achievement speed runs. Upload and share your save with the world.
nomicon - The Dark Arts of Advanced and Unsafe Rust Programming