Nate McMaster

Fixing this will be tricky to do without breaking anyone who has come to depend on existing behavior, but I think it should be possible. Basically, you would need to...

Putting this into the 3.0 milestone as something to consider.

It was a deliberate choice because it is a simple, sensible default. Bearing in mind that the parser gets an array of strings, consider some of these ambiguities: ```c# {...

> Honestly, only the first option is close to me. If you think there is enough value here, I'd take a PR as long as the syntax remains unambiguous. >...

Something like `PeekableEnumerator` seems like a promising idea. The pseudo-implementation you suggested would need to be fleshed out and tested quite a bit more, but the general premise (i.e. using...

Putting this in the 3.0 milestone. I think there is value in providing functionality to help with this problem.

So, in other words, you want all the goodness of `CommandLineApplication.Execute` without the requirement to implement an OnExecute method on the Settings class? If so, this is something I've considered...

Dependency injection. Yeah, the heavy lifting is done. This is really a matter of designing an API that works well. It's possible to implement some of this on your own...

I have two suggestions: 1. You could leverage the "Parent" convention to get a pointer to the parent subcommand, and then invoke methods on that parent class (including the OnExecute...

I'm open to suggestions on how to implement this one. Adding the help-wanted label. I think you're right...it is sort of a chicken and egg problem in the code's current...