parking_lot VS argh

parking_lot is being considered for replacing the mutexes in std. Last I checked the libs team did a review of its internals and left some feedback for the implementor to address before it could be considered further: https://github.com/faern/parking_lot/pull/1

https://github.com/google/argh is another minimal library for CLI argument parsing that could be in the list

My go-to is argh[1], as it's more lightweight while still providing a nice derive-based API.

[1]: https://github.com/google/argh

It'll panic if the path contains non-UTF8-able bytes.

Yes clap needs a lot of boilerplate that small programs don't always need, but if you're going to simplify it, I don't think having a bunch of arguments given to the main function is better than having an option struct as in argh. Such an option struct can be given to other functions from the main, can have dedicated consistency check or completion methods, etc.

Typically programs are configured through a config object. People like to use things like clap, structopt, or argh for passing in arguments through the CLI https://github.com/google/argh. You can also use the env! macro for embedding values in at compile time, or by going through the std::env::var infrastructure for runtime env vars.

Until the argh crate bumps their version I cannot updater the version on crates.io so the install command currently is: cargo install --git https://github.com/mkatychev/darkroom

Ahh. The secondary reason I discounted Argh as "unsuitable for purpose" after "Doesn't support using OsString under the hood".