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 bit ugly, but sometimes the error while parsing an argument seems to take precedence over anything (including other errors) that might be encountered later:
pubtraitOptions<Arg:Arguments>:Sized{/// Apply a single argument to the options.fnapply(&mutself,arg:Arg) -> Result<(),Error>;// Rest basically unchanged; the default `parse` impl would simply call `parse()?` instead.}
What do you think?
The text was updated successfully, but these errors were encountered:
I've tried to hold of on this and figure out a system where all errors are generated by the parser and the Value trait, but I don't see any way to model this behaviour with that (if even I think that printing --help is the more "correct" thing to do). So, yeah, this is probably a good idea!
This is a bit ugly, but sometimes the error while parsing an argument seems to take precedence over anything (including other errors) that might be encountered later:
See also uutils/coreutils#4254 (comment) for further examples.
I propose changing the interface to:
What do you think?
The text was updated successfully, but these errors were encountered: