Stephen M. Coakley

There is no tracking issue, but there's a milestone here: https://github.com/sagebind/isahc/milestone/13. There is no due date for version 2.0, it'll be ready when it is ready.

Here's the extprim PR: https://github.com/kennytm/extprim/pull/18. It hasn't been published yet though: https://github.com/kennytm/extprim/issues/19.

I have an Apple device I would try and reproduce on, but we haven't upgraded to Big Sur yet due to company policy. But I _can_ try to reproduce with...

Unfortunately I was not able to reproduce the compilation error on my machine with Xcode 12.3 installed, so it probably is related to Big Sur specifically and not the Xcode...

I'm not sure what the advantage of using that API would be over using something native such as the `url` crate. This does run into the problem though of backwards...

I think readline is only used for the lua command-line interpreter, right?

> Note that we could separately discuss whether this `curl` crate should have built-in (behind an optional crate feature) `http` interop support, now that they've had their `1.0.0` release? This...

The historical way to determine the HTTP version used in a request/response would be to examine the first line of the header block from `CURLOPT_HEADERFUNCTION` (via [`Easy::header_function`](https://docs.rs/curl/latest/curl/easy/struct.Easy.html#method.header_function) or [`Handler::header`](https://docs.rs/curl/latest/curl/easy/trait.Handler.html#method.header)). Though...

This already requires a bump to MSRV since `once_cell` 1.15+ does not compile under Rust 1.51 last I checked, which is why the version range was specified that way. But...

It is possible to use libcurl in an asynchronous fashion using the [non-blocking multi API](https://everything.curl.dev/libcurl/drive/multi), you can see an example of how this is done [here](https://github.com/alexcrichton/tokio-curl) (though that is pretty...