Stephen M. Coakley

If you are referring to https://github.com/alexcrichton/curl-rust/pull/433, there are several issues preventing it from working, which is why it was never merged. I am not too surprised that it does not...

It should be possible to rewrite the test to not require `mio_extras`, taking a cursory glance at the offending test.

Seems somewhat reasonable, though I'm not sure the best way of doing this. Detecting based on the version of the host system might work, but that doesn't necessarily tell you...

I'm not sure that auto-discovery based on curl version is a good idea. If we dynamically link because `static-curl` isn't enabled and curl is available on the build machine, we...

> I don't think the system you're talking about though @sagebind jives well with what we already have today. The majority of curl's new features go through options which means...

I think this would _have to_ be implemented as a separate feature based on my understanding of how features in Cargo work. Features are additive; opting out of a feature...

I can't read Alex's mind, but I imagine that the curl bindings were created just for HTTP access, and no one really needed anything else from libcurl, so it was...

The right way to toggle static builds on different targets for downstream crates will probably be with using target-specific feature sets, which is currently in development: https://github.com/rust-lang/cargo/issues/7914. This doesn't affect...

Hey, glad you found it anyway! That's fine; it's better to be stable and optional than sketchy and in the core. However, I'm convinced that the core needs a better...

Also, I'd love to help out! I've got some Windows machines to test on (not my primary OS though) and could probably play with the possibility of Windows support.