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

pool: use Executor trait instead of concrete type #47

Merged
merged 1 commit into from
Nov 15, 2023

Conversation

howardjohn
Copy link
Contributor

Alternative to #24.

Currently, Pool cannot be used at all. It requires a concrete Exec, and that is private. The #24 PR simply made Exec public. However, there is already other things in this crate that require an Exec (legacy::Client).

This adapts Pool to follow the same pattern as used for Client, taking in a trait.

This change is NOT a breaking change, as Pool cannot be used at all currently, so no one could be broken.

Alternative to hyperium#24.

Currently, `Pool` cannot be used at all. It requires a concrete `Exec`,
and that is private. The hyperium#24 PR simply made `Exec` public. However,
there is already other things in this crate that require an `Exec`
(`legacy::Client`).

This adapts `Pool` to follow the same pattern as used for `Client`,
taking in a trait.

This change is NOT a breaking change, as `Pool` cannot be used at all
currently, so no one could be broken.
@seanmonstar seanmonstar merged commit e91fba8 into hyperium:master Nov 15, 2023
15 checks passed
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.

2 participants