-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should structopt re-export paw
?
#407
Comments
I say we can gate the reexport under |
Wait, we can't reexport it because, astonishingly, On the other hand, if the end user of your crate enabled the feature, they depend on paw already, and we can depend on it without extra trouble. @TeXitoi what do you think about it? |
Fat chance.
We can't depend on paw because we have a feature named I'm afraid this is just unsolvable with no hope on horizon, so I think the only solution is to avoid using the feature. IMHO, it doesn't have any value except giving you warm nostalgic feelings from good old C days when you got the args passed directly to main. |
I did it! |
clap-verbosity-flag
is a crate that provides a reusable set of arguments. When someone tried to useclap-verbosity-flag
withpaw
, it broke:structopt
has thepaw
feature on but the symbolpaw
isn't visible withinclap-verbosity-flag
to be able to compile.Currently structopt re-exports clap. Should it also re-export paw?
The text was updated successfully, but these errors were encountered: