Open Stupremee opened 2 years ago
Is there a reason you don't want to just bring in the whole http crate? The dependency is already quite light. I don't think moving things to their own crate makes anyone's life easier.
The reason is that http
does not have support for no_std
environments.
Maybe a better goal would be to allow http to support no_std similar to how bytes
has no_std support. I don't think the correct solution is to create another crate.
Sure, that would work as well!
+1 for this
My use case is an HTTP client running in embedded hardware, hope this PR(https://github.com/hyperium/http/pull/563) can get some feedback :) Ideally it would be nice if http
works without alloc
but that seemed like a mayor refactor and possibly breaking change.
Hello,
I'm currently in need of a correct
Uri
parser, and I believe the best URI implementation is the one in this crate. However, I don't want to add the wholehttp
crate as a dependency. So, it would be very helpful if there was an additional crate just for URI parsing.