-
Notifications
You must be signed in to change notification settings - Fork 143
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
don't depend on hyper/tcp feature by default #100
Conversation
On fuchsia, we don't support the mio and tokio runtime yet, and so in order to use hyper-rustls, we need to compile it with `default-features = false`. Unfortunately, in rustls#96, @CryZe added a hard requirement for the hyper "tcp" feature, which pulls in the tokio runtime. To restore our ability to use hyper-rustls, this patch removes the "hyper/tcp" hard feature requirement.
f87c8b9
to
0f432b3
Compare
I just checked, and it actually looks like we don't even need this feature for |
Whoops, sorry about that ^^' |
@CryZe No worries! This isn't blocking us yet, I'm just doing prep work to update to hyper 0.13. Thanks for doing the upgrade! |
@ctz gentle ping :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks @lucab! Would it be possible to also get a 0.19.1 release cut for this change? |
You'd need @ctz for publishing a new crate version. He usually batches GH activity around the weekend. |
Awesome, thanks! |
On fuchsia, we don't support the mio and tokio runtime yet, and so in order to use hyper-rustls, we need to compile it with
default-features = false
. Unfortunately, in #96, @CryZe added a hard requirement for the hyper "tcp" feature, which pulls in the tokio runtime.To restore our ability to use hyper-rustls, this patch migrates the "hyper/tcp" hard feature requirement to an optional "tcp" feature. Note that we don't need to change the default case, because the "hyper/runtime" feature already depends on "hyper/tcp".