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
In many CLI parsers, it is a common convention to use -- as a special argument which will force all subsequent arguments to be read as positional/"free". After a quick glance at documentation and code of this crate, I could not find any information on this. How does this crate currently handle the presence of -- options? If it doesn't then consider this a feature request.
The text was updated successfully, but these errors were encountered:
it's been added in #100
but no updated version since then's been published, so 0.2.21 that you see on crates dot io, is from 5 years ago and doesn't have it in.
possibly not published yet due to the need to ensure it doesn't break anything:
The getopts library is used by rustc, so we have to be careful about not changing its behavior.
In many CLI parsers, it is a common convention to use
--
as a special argument which will force all subsequent arguments to be read as positional/"free". After a quick glance at documentation and code of this crate, I could not find any information on this. How does this crate currently handle the presence of--
options? If it doesn't then consider this a feature request.The text was updated successfully, but these errors were encountered: