You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reqwest adds quite a bit of time to compile times in projects where it isn't needed. Removing reqwest from our project reduced compile times by about 30s. We already have hyper in the dependency tree via axum so it was mostly free.
Willing to put up an implementation of this if it's supported.
The text was updated successfully, but these errors were encountered:
I believe this is a good idea, yes.
What exactly would be the advantages feature wise? As reqwest is based on hyper itself, but I assume you have to implement a ton of stuff yourself.
It would definitely be a feature reduction actually. Proxy support is something that we've intentionally left out of scope (because we don't use one). The reduction in feature scope reduces compile times and we find the trade off advantageous in that way.
Reqwest adds quite a bit of time to compile times in projects where it isn't needed. Removing reqwest from our project reduced compile times by about 30s. We already have hyper in the dependency tree via axum so it was mostly free.
Willing to put up an implementation of this if it's supported.
The text was updated successfully, but these errors were encountered: