Remove send & sync bounds and permit non-Send IO and Body types #168
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Both clients and servers support customized executors, including local thread executors. There are still some limitations due to the SharedService type converting the wrapped service to dyn Service + Send + Sync. Its not easy to drop the bounds there, but maybe an alternative approach is possible. As well, bodies are still limited to be Send due to the use of boxed futures. Eliminating the remaining box futures will solve this problem.
alexrudy
force-pushed
the
fix/remove-send-sync
branch
from
7f3c170 to
8a3f133
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.