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.

Sign up for GitHub

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

Jump to bottom

Drop Send requirements on the future returned by the service #40

Merged
merged 3 commits into from
Oct 19, 2023
Merged

Drop Send requirements on the future returned by the service #40

merged 3 commits into from
Oct 19, 2023

Conversation

LukeMathWalker
Copy link
Contributor

The current bounds appear to be too strict when it comes to Sendness, preventing the usage of auto in combination with an implementation of Executor that's designed to spawn !Send futures.

seanmonstar
seanmonstar approved these changes Oct 19, 2023
View reviewed changes
Copy link
Member

@seanmonstar seanmonstar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@seanmonstar seanmonstar merged commit 1ed4c2c into hyperium:master Oct 19, 2023
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@seanmonstar seanmonstar seanmonstar approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@LukeMathWalker @seanmonstar