Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "Add impl Service<http::Request<Body>> for Client" #2397

Merged
merged 1 commit into from
Aug 19, 2024

Conversation

seanmonstar
Copy link
Owner

From #2356

This reverts commit 522216e.

There was a report in #2395 that the second impl causes inference problems. While not a semver problem, it now makes me wonder if it's worth having the second impl. It's not hard for anything to have a middleware layer that converts the types.

cc @alekseysidorov

@seanmonstar seanmonstar merged commit 68127f0 into master Aug 19, 2024
36 checks passed
@seanmonstar seanmonstar deleted the revert-another-service-impl branch August 19, 2024 21:01
@alekseysidorov
Copy link
Contributor

I wonder if tower has just released a 0.5 version, which means that when updating reqwest to it, you'll have to do a breaking changes anyway. So can we add this additional Service implementation to the 0.13 reqwest version?

@seanmonstar
Copy link
Owner Author

The tower-service crate which is what the Service trait comes from has stayed stable. tower is a bunch of goodies on top, but we don't depend on it publicly in reqwest.

@omarabid
Copy link

Does gating this behind a feature flag solves the stability/inference issues?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants