We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Address
Mailbox
Context
As part of doing #122, I started to form the following vision:
Chan
Sender
Receiver
Putting all of this together, we could realise an API like this:
let (mailbox, address) = Mailbox::bounded(5); tokio::spawn(xtra::run(mailbox, MyActor::new()));
With run being implemented more or less like what we have today.
run
The text was updated successfully, but these errors were encountered:
I think this makes sense!
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
As part of doing #122, I started to form the following vision:
Chan
should be the core channel implementation of the library, Move channel logic intoChan
#122 gets us most of the way thereSender
andReceiver
only really add an opinionated interfaces on top of it, plus reference countingSender
norReceiver
are publicly exposed, meaning I think they don't actually have to existSender
can be completely inlined intoAddress
, removing an entire layer of indirectionReceiver
can be promoted to a type calledMailbox
that could be publicly exposedContext
would be something that is constructed only temporarily for the invocation of a handler (I think we discussed this idea at some point)Putting all of this together, we could realise an API like this:
With
run
being implemented more or less like what we have today.The text was updated successfully, but these errors were encountered: