-
Notifications
You must be signed in to change notification settings - Fork 64
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
Rename use-rustls
and use-openssl
features
#42
Comments
I think option (2) would create even more confusion, because in many ways Option (1) makes sense, but I'd rather not break the naming for downstream users of the library. We can keep this issue open an potentially do this as part of a larger refactoring that would already break the naming of features for instance. Other than that, I consider this very low priority |
By the way, if I read the link you posted correctly it's not even necessary to rename crates: it seems that cargo is smart enough to map features with the same name of a crate to enabling that crate. In their example they show that by making |
No, that would not work :( You will also need to enable |
Well in our case we don't really need to have |
According to Rust API guidelines feature names with
use-
prefix considered wrong: https://rust-lang.github.io/api-guidelines/naming.html#c-featureThis is justified, since ppl looking for features will frequently use
rustls
instead ofuse-rustls
and will report issues - we had plenty of them inrust-bitcoin
with similarserde
situation.There is two options:
rustls_crate = { package = "rustls" }
+extern crate rustls_crate as rustls
inlib.rs
and rename features intorustls
tls
andssl
I am pro second option
The text was updated successfully, but these errors were encountered: