Cannot pass negative values to NargsValueFlag<double> about args HOT 3 CLOSED

This is definitely a bug. This appears to happen inside ParseArgsValues at this point because it checks if the argument has the short or long prefix to be a flag. if nargs.min != nargs.max. This should probably instead only check size < nargs.min, but it still will fail on ambiguous cases (such as if -a needs 1 or 2 arguments, but the second argument is negative, in which case there's no unambiguous and reasonable way for the library to determine whether it is supposed to be a negative number or a short flag with a digit character. It would be potentially possible to try to match against all flags again, but that's messy, and would cause exsiting use of your programs to break if you happen to add a digit flag that somebody else is using, not to mention if the program is used dynamically, it might sometimes work and sometimes not depending on the ambiguity of the digit, and might sometimes even silently do the wrong thing).

from args.

This is fixed with version 6.2.4

Note that this will still fail if you specify a negative value (which has the same prefix as the short flags) when you're over the Narg minimum threshold. This is intentional for the reasons stated above. So for your example, if your -a flag is Narg {1, 2}, the second value will not be able to be negative, because adding the digit flag later would cause a failure. Nargs with variable value counts already cause ambiguity quite easily, so that particular case won't be workshopped. You can fully avoid this by using a ValueFlagList or PositionalList.

from args.

Thanks man! I will update to 6.2.4
Cheers

from args.