Waiting for the stable version.
Also I can't find some features until I Google it, and finally I find an answer from Stack Overflow, but it's removed since some newer release.It makes me sad.
So could you write more comprehensive documentation?
Many thanks.
Hi there! A stable version (1.0) in some sense is getting closer.
Method, StatusCode, HeaderMap, Request, Response, etc) have moved to the http crate, and are quite stable. I wouldn't expect much changes other than very minor paper cuts fixed when we mark that as http v1.0.Client and Server types have seen some re-design, but are in a much better place. I suspect they also won't change too much more, other than cleaning up some configuration options.futures. There is a plan to move them to std::future, and have language support for async/await. However, this will mean a big change to the ecosystem from the current futures v0.1 crate. This is the main blocker affecting everything, really.After future is able to stabilize, I suspect a hyper v1.0 wouldn't be too far behind.
Got it, thanks for your answer.
@seanmonstar Thanks for explanation. I faced with the same issue as da2018. I think it would be awesome to publish this plan to the main page.
P.S. async/await - cool stuff.
Most helpful comment
Hi there! A stable version (1.0) in some sense is getting closer.
Method,StatusCode,HeaderMap,Request,Response, etc) have moved to thehttpcrate, and are quite stable. I wouldn't expect much changes other than very minor paper cuts fixed when we mark that ashttp v1.0.ClientandServertypes have seen some re-design, but are in a much better place. I suspect they also won't change too much more, other than cleaning up some configuration options.futures. There is a plan to move them tostd::future, and have language support forasync/await. However, this will mean a big change to the ecosystem from the currentfutures v0.1crate. This is the main blocker affecting everything, really.After
futureis able to stabilize, I suspect ahyper v1.0wouldn't be too far behind.