feat(core): implement Context::send
in the builder-like manner
#142
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.
Imperfect draft of turning
Context::send
into chained builder. Adding behavior settings forContext::send
could be annoying, we already have functions likeunbounded_send
,send
,send_to
,unbounded_send_to
,try_send
,try_send_to
and so on. With turningsend
into builder, we could achieve having only one function in theContext
:Context::send
, actions performed on that builder could be divided in two categoriesOutcome
Function which finishes building of envelope and sends it, such as
ctx.send(..).try_()
- try send without waiting for available place in the mailboxctx.send(..).unbounded()
- send envelope unconditionallyctx.send(..).await
- wait for place in the destination mailbox and sendParameters
.to(..)
- destinationMoreover, we could elide
request
andrequest_to
functions as well, but it requires more thought though, sincectx.send(..).resolve().await
looks nice, butctx.send(..).all().await
seems confusing (Maybe unifyingsend
andrequest
interfaces is quite unfortunate?)