Joshua Verburg-Sachs

Since you think it's a good approach I'll move forward with this: - I'll cook up some examples - Will add test coverage I believe it would be possible to...

> @vsachs Sorry for the delay. I've had some extra time over the weekend to look at this PR. As I said earlier -- it is fine as-is, I just...

> @vsachs something with the implementation that causes interesting failure, i've added a TestPos8 test to show it, within this test you can also move around "-s", "some string" to...

> Also I left a few comments with some minor things in current code. @akamensky Sorry but I don't see your comments anywhere? Did github swallow them?

> > I see roughly three approaches: > > > > 1. Leave as is > > 2. Cause positionals to be parsed after flags are parsed. This is probably...

# On ordering issue Okay, I will attempt to achieve the proposed outcome, which you've outlined in the code block clearly. # On required vs optional Option 1 seems reasonable...

Parsing has been changed to the desired ordering and option 1 is utilized for positionals. Subsequently I've enabled defaults for positionals and added a GetParsed() function to the argument so...

> @vsachs since you've invested into this PR so much time and effort (and since I have limited time to work on this lib), I have invited you to collaborators....

Just ran into this myself, actually. Great library btw, was able to integrate with it in about 30 minutes. Only snag so far is this problem: ``` triple super debug:...

> I think if positional is marked as required and there is no value available to fill it -- should throw an error. If we always throw an error when...