Compatible with async-std.

[gmg137]

• Compatible with async-std.
• Fix test errors.

Note: reqwest is pure rust, isahc relies on curl.

[Empty2k12]

Hello! Thanks for openig this PR! I think it makes a lot of sense to support all runtimes available.

DO you think, however, we could support async-std only with a feature-flag and use reqwest when users do not opt into async-std. I think we can select the http client dynamically via the feature flag. Tests in CI would nbeed to run twice, once with each http library.

[gmg137]

hello, providing multiple optional http clients is a good idea, but it can add to the complexity of use. The user does not perceive the difference between reqwest and isahc in terms of functionality, so whether or not to use feature flag requires you to make the trade-off.

[Empty2k12]

reqwest is pure rust, while isahc is dependent on the OS. I think that should be opt-in :) Interms of complexity, maybe a common HTTP Abstraction for the library could be provided which takes care of sending requests with isahc or reqwest depending on the feature-flag.

[gmg137]

Indeed, it makes more sense to offer an optional feature flag. This requires you to redo the global feature design and update the instructions file. You can just change my PR, or tell me what needs to be done.

[MTRNord]

Same order of arguments here too according to my IDE

[MTRNord]

Works on my PC :)

[Empty2k12]

@gmg137 How do you think should the global feature design be changed? I thought it might be possible to add a feature flag for toggling between async-std/tokio

[gmg137]

@Empty2k12 Agreed, adding a feature flag is by far the most common practice.

[Empty2k12]

This is now implemented in #72. Thanks for your interest in the project.