You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a slightly breaking change - not enough to warrant a label.
Currently, using named values -f <file> <mode> requires you to set multiple(true)...but this isn't correct logic. By this token, someone could legally do:
$ myprog -f some.txt fast -f other.txt slow
This may, or may not, be what the developer wanted. Setting multiple(true) shouldn't be a requirement for named values...only for unnamed multiple values. This allows the developer to decide which style of argument he wants, multiple allowances, or multiple values.
The text was updated successfully, but these errors were encountered:
This is a slightly breaking change - not enough to warrant a label.
Currently, using named values
-f <file> <mode>
requires you to setmultiple(true)
...but this isn't correct logic. By this token, someone could legally do:This may, or may not, be what the developer wanted. Setting
multiple(true)
shouldn't be a requirement for named values...only for unnamed multiple values. This allows the developer to decide which style of argument he wants, multiple allowances, or multiple values.The text was updated successfully, but these errors were encountered: