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
I was looking at argh just now and it looks pretty good.
Normally I avoid this sort of #[derive(CliArg)] sort of deal because I tend to worry that the trait won't be expressive enough... but if it's similar enough to the traits I'm already writing, then what's the problem? It'd be cool to test it out on something with reasonably complicated args like truth and see if I have finally found the one good CLI parsing library in the ecosystem, so that I can finally stop stressing out every time I have to parse args in rust.
Some of the stuff on there seems concerning. (no -vsnr, and they (agreeably) advise against the equals sign in -o=<my_output_file> while using language that would appear to also (questionably) forbid --output=<my_output_file)...
The text was updated successfully, but these errors were encountered:
I was looking at
argh
just now and it looks pretty good.Normally I avoid this sort of
#[derive(CliArg)]
sort of deal because I tend to worry that the trait won't be expressive enough... but if it's similar enough to the traits I'm already writing, then what's the problem? It'd be cool to test it out on something with reasonably complicated args liketruth
and see if I have finally found the one good CLI parsing library in the ecosystem, so that I can finally stop stressing out every time I have to parse args in rust.It mentions Fuschia and I found this: https://fuchsia.dev/fuchsia-src/concepts/api/cli
Some of the stuff on there seems concerning. (no
-vsnr
, and they (agreeably) advise against the equals sign in-o=<my_output_file>
while using language that would appear to also (questionably) forbid--output=<my_output_file
)...The text was updated successfully, but these errors were encountered: