Kevin K.

Looks like a good start! It's a small nit, but let's change the feature name to `iter_matches` because `iter` is somewhat ambiguous and may conflict with other types of iteration...

Yep, I'd actually prefer it that way because it's easier to comment and review :smile: :+1:

> [I] am trying to call map() on each arg I find to invoke the appropriate handler function based on the argument passed... For a while I was floating around...

> Resolved by derive (and partially by value_of_t* methods). Exactly. I'm describing a problem/issue that existed prior to derive macros. The "handlers" was just a common theme that popped up...

Yours is not a super common case. Essentially, your CLI is a facade for a builder API? A few things about what you mention stood out to me (emphasis mine):...

Although it's a more advanced topic, and probably defeats the purpose of what you're trying to do, you could combine your own Custom Derive macro, and do something like `#[derive(Clap,...

The clap derive macros are the new big feature of clap 3.x which is still in beta and thus not formally released yet. So the documentation is still lacking. The...

Re-energizing this topic. Not necessarily for action prior to 3.0 release, but something to keep in our mind and begin to tackle as available. My comment from #1891 > Along...

Just so my thoughts are known, I don't believe we need to remove all dependencies and features for the smallest possible size. What I *do* think is that we should...

Doing a `--no-default-feautres --features std` build on a simple: ``` App::new("foo").get_matches(); ``` Gives us this output via `cargo bloat` in release mode: ``` cargo bloat --crates --release [..] Analyzing target/release/fake...