feat!: add support for bounded/unbounded mailboxes #29
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.
Closes #3 and #28
This PR changes how the fundamentals of kameo works, but adds support for choosing the boundedness of actor mailboxes. The actor mailbox can be set when implementing
Actor
with thetype Mailbox = BoundedMailbox<Self> or UnboundedMailbox<Self>
associated type.As unbounded channels differ in asyncness than bounded channels, a new builder syntax has been introduced when sending messages to actors. The types are
AskRequest
,TellRequest
, andQueryRequest
. These are returned an ActorRef's with the.ask(...)
,.tell(...)
,.query(...)
methods, and support customizing timeouts.Sending a message with a reply would look like
my_actor_ref.ask(Foo { ... }).send().await?;
, and sending a message without a reply looks likemy_actor_ref.tell(Foo { ... }).send().await?;