remove async-trait #33
Closed
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
al8n
force-pushed
the
remove-async-trait
branch
from
20e42e5
to
16d7c47
Compare
| pub trait ServiceCore: Sized + ServiceData { | ||
| /// Initialize the service with the given state | ||
| fn init(service_state: ServiceStateHandle<Self>) -> Result<Self, super::DynError>; | ||
|
|
||
| /// Service main loop | ||
| async fn run(mut self) -> Result<(), super::DynError>; | ||
| fn run(self) -> impl Future<Output = Result<(), super::DynError>> + Send; |
There was a problem hiding this comment.
So, for async methods that return something that need to be send we need to use impl Future instead of async?
There was a problem hiding this comment.
Yes, if we use async, by default there is no Send bound.
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.