argparse-rosetta-rs VS cargo-semver-checks

It's clap and bpaf nowdays from fully featured ones. https://github.com/rosetta-rs/argparse-rosetta-rs

"not enough arguments" is nice, but what arguments do you need to pass? Use cli option parser such as bpaf or clap to deal with that kind of stuff - they will generate --help for you for example. https://github.com/rosetta-rs/argparse-rosetta-rs

We link to https://github.com/rosetta-rs/argparse-rosetta-rs for a full list. In such a competitive category, I don't think I can really recommend anything that doesn't handle non-utf8 arguments. I am considering adding bpaf to the recommendations in the "full" category, as they recently added this support.

Latest benchmark results Diff of clap v3 to clap v4

There's a nice overview made by /u/epage https://github.com/rosetta-rs/argparse-rosetta-rs/blob/main/docs/tradeoffs.md

We collaborated on the trade-offs document though that doesn't reflect the upcoming release which expands on the parser flexibility.

For parsing people tend to use a parser, some are listed here: https://github.com/rosetta-rs/argparse-rosetta-rs

I've updated argparse-rosetta-rs (formerly argparse-benchmarks-rs).

If you'd like to dig deeper, here are some links:

- cargo-semver-checks: https://github.com/obi1kenobi/cargo-semver-checks

- Trustfall query engine, which powers cargo-semver-checks: https://github.com/obi1kenobi/trustfall

- Trustfall playground, where you can query Rust library APIs in your browser -- for example, "which structs in `itertools` are importable by more than one path": https://play.predr.ag/rustdoc#?f=2&q=*3-Structs-importable-f...

- 10min conference talk on Trustfall: https://www.hytradboi.com/2022/how-to-query-almost-everythin...

I'm also giving a talk at P99 CONF in a few months about how Trustfall's new optimizations API made cargo-semver-checks over 2300x faster: https://twitter.com/PredragGruevski/status/16893002495908003...

I strongly recommend that anybody creating new error types for public APIs read Study of std::io::Error by u/matklad to see some ways that error types can [need to] be future-proofed. I don't know if cargo-semver-checks can catch these issues when they're generated by a macro, but it'd be something people using this crate should carefully look into.

cargo-semver-checks will implement a check for cases like this, and many other hazards like it. The check will be major, or minor, or just a hazard — whatever the overall community decides is right.

Full release notes: https://github.com/obi1kenobi/cargo-semver-checks/releases/tag/v0.18.0

Release notes, TL;DR: Rust 1.65+ only, no more false positives due to moved+re-exported items.