Thomas Eizinger

Introduce top-level `recv_future` module

3

This creates consistency with the `send_future` module. To achieve this, we temporarily make the fields of `Receiver` public. This will go away once we merge #158 because it allows us...

Document features of `Context::stop_all`

6

Document the findings of #119.

Have `Error::Disconnected` contain the actor name

8

Makes for better error messages.

Roadmap to 0.6

3

Lots of good PRs have been merged into master since the last release. I'd like to make an effort to finalise the public API so we can push a new...

Re-focus public API on `Address` & `Mailbox` aka short-lived `Context`

1

As part of doing https://github.com/Restioson/xtra/pull/122, I started to form the following vision: - `Chan` should be the core channel implementation of the library, #122 gets us most of the way...

Experiment with a functional API

2

This is probably more something to be added in an extension crate, but it would be cool to be able to define actors from closures: ```rust let initial_state = 0u64;...

Introduce `SendFuture::repeat_every`

3

Extracted out of #71. This should be introduced via an extension crate to not grow the core API of xtra unnecessarily. It is important that this must work only on...

Document goals and non-goals of xtra

6

In https://github.com/Restioson/xtra/issues/119 and other places, we have discussions that ultimately come down to optimising for different goals. I am opening this issue to propose and discuss a manifest that states...

Benchmark against mpsc channels

10

xtra is by design small and thus, I think a big contestor for people making a decision on what to use might be tokio's or futures' mpsc channels, spawned as...

Add proc-macro for convenient creation of `Handler`s

15

Currently, defining a `Handler` requires the usage of `async_trait` and filling in various elements into a trait impl. In theory however, a macro can learn all required pieces of information...