Open dtolnay opened 7 years ago
I don't know if this was discussed in the meeting, but what are your thoughts regarding hyper async and stabilizing request?
Should 1.0 wait for a stable release of hyper async?
Or should there already be a SyncClient
with a backwards compatible API once hyper async arrives?
It was mentioned that since an async client will need to expose Future
, and the futures crate won't stabilize before reqwest, then reqwest 1.0 will just have a sync client, and and reqwest_async
will live seperately as an unstable thing. When it can stabilize, it could be merged into reqwest and released as v2.0.
That said, to reduce breakage of reqest v1 -> v2, the Client naming issue is relevant here.
Lots of these issues are doc or examples. I'm thinking about writing examples using https://httpbin.org. Would that be good, or did you have other ideas in mind?
It's fine for the example to refer to httpbin, just because the example isn't in a fn main() {}
, so we don't have the doctests actually making requests.
Hi large part of docs (including part of landing page) are missing links when referencing symbols. Should these be corrected (assuming yes from log crate evaluation)?
This is the tracking issue for the evaluation performed by the libs team this week.
Stabilize some of the foundational types in a separate crate