getopts
getopts copied to clipboard
rust-lang
The getopts repo maintained by the rust-lang project
The 'contributing' section of the readme contains note that the `getopts` crate is used by compiler and contributors must be careful to not break anything. Is there also consensus on...
There are a lot of pieces to this that are uncovered in the example supplied in the docs. More examples would help to better show off how to use this
If `matches.opt_present` is called with a not-defined option, that should either be a compile-time error (somehow) or it should return false; currently it panics instead.
maybe the wording here isn't ideal, but this PR is so that "we"(or you) don't forget to address it. Can always change wording later, before merging. see comment: https://github.com/rust-lang/getopts/issues/104#issuecomment-2211736049
It would be useful to have a way to specify an option which uses its *last* occurrence as its value; e.g. ```sh cmd --foo fizz --foo buzz ``` ```rs assert_eq!(matches.opt_str("foo"),...
