CreepySkeleton

clap has `Arg::validator` that is called on every _value_ passed in. And of course, you can always iterate over `std::env::args()` and map it as you please; you don't really need...

> I want my CLI to accept options yes|no but I want the value held my context struct to be some concrete type Resolved by derive (and partially by `value_of_t*`...

@bradwood Out of morbid curiosity, what is the core problem you're trying to solve? Why do you think `map` is a good way to approach this kind of problem? I...

Before we more any further, would you please test it in release mode 😄? Nobody cares about debug binaries, release the ones of concern here.

main.rs ``` use clap::*; fn main() { App::new("app").get_matches(); } ``` With lto enabled (release build, no default features) ``` CreepySkeleton@builder:~/workspace/probe$ cargo bloat --crates --release [...] File .text Size Crate 19.4%...

To clarify my statement about embedded: * On something like Rabspery PI clap will fly marvelously; you won't even need no-std there. It's close to a real PC after all....

> Also, one other note: IIRC, cargo bloat has an option to list binary size by function. That might also be useful to look at for decreasing binary size. Sometimes...

And maybe require attaching a bit of context ```toml [unaffected_consumers] clap = { version = ["2"], reason = "never triggers, only trusted input", discussion = "link to thread" } ```...

Also, when a linux distro maintainer packs your crate as `.deb`, his packing system requires these files - `LICENSE-*` - to be present, I think for every crate in workspace,...

@pksunkara No, we wouldn't. Switching to a fork would mean that `Yaml` types became different, exactly the reason we can't just bump it to `yaml-rust 0.4`. I suggested to switch...