Does "Core" assume that arguments 'Always' have to be ordered?

[MarkMichaelis]

Given getuser.exe <username> <age>, two or more arguments, where age can only be an integer and username cannot be an integer, do we provide any functionality try to coerce into username and age values regardless of argument order?

Note:

• It is possible to sometimes programmatically determine the order.
• If we can't determine the order we can report an error that arguments are ambiguous.
• The programmer can always convert the arguments to a string array (or two string arguments) and then address order independently from us.

[jonsequitur]

ParseResult.Tokens provides the ordered array of strings that were parsed, so this approach can be layered on top of the existing core library. (Currently, the only ordering assumption is that arguments apply to the closest eligible option or subcommand to their left.)

[MarkMichaelis]

As discussed with @jonsequitur and @Keboo:
We will try to support option arguments where given no option name, we will determine the name based option position within the command.

[MarkMichaelis]

Duplicate of #29.