Kevin K.

@emme1444 try this: *note:* You may not need all these deps, but I don't have a machine to test which ones aren't required at the moment. ``` $ sudo apt...

@michaeltarab The yshui fork has been working well for me, and seems to get updated every few days so it's definitely active. However, it does not include the kawase blur...

Sorry for the late reply, it's been a busy week! This is related to #568 and something I very much want. The implementation you've outlined is pretty close to what...

`app_from_crate!` could use whatever crate these would get spun off into so I'm not too concerned from that angle. I'm more worried that because these aren't clap related, what if...

> Since a deprecation is not a breaking change, should we move this out of the 3.0 milestone? Good point. My point was just to deprecate for 3.0 like @pksunkara...

Sorry for the wait, I've been on vacation with my kids this past week :) Do you mean iterating over only positional values, or over *all* args that have been...

To make sure it's not an `XY` problem, how does your CLI work with the order of args? I've always seen conflicts/overrides as the main driving factor for when order...

Another more lengthy option (but arguably more correct) is instead of returning an Iterator of some custom data type tuple, returning the [`MatchedArg`](https://github.com/kbknapp/clap-rs/blob/07c15d28d94ffb0ba52b895cd75404c73ed5d10a/src/args/matched_arg.rs) itself. I say more lengthy because you'd...

Right now, clap uses a `HashMap` to hold the matches, which is inherently not in order. Switching to an `IndexMap` would be basically a drop in replacement, but because it's...

> I feel hesitant adding an iter method to ArgMatches; it feels like a duplicate of indexmap's functionality. ArgMatches.args: IndexMap is already public, so what's wrong with the user doing...