Alexey Aristov

+1

If I understand your question - you are trying to find a way of how to create an actor that wraps a mutable database connection. Of course, it's not a...

@filipcro of course, connection pool can be used/created, but this is slightly different topic.

As far as I know, rust currently does not support _async_ in traits. Maybe, it makes sense to create AsyncActor that returns _Future_ from _recv_ (and other callbacks).

Meanwhile, I created a small prototype (based on the _async_trait_). I will take a closer look at what I've got and create a branch, so it could be reviewed. ```rust...

Here is the proof of concept: https://github.com/aav/riker/tree/async_recv There are two alternatives ahead - change all callbacks to async, including Receive, ActorFactory*, and, probably, some other parts of API. This is...

> > For consumers who don't need async, the extra trouble will be minimal. > > how so? for those who don't care if recv is async, the extra steps...

It looks like Travis hanged due to the race described in the _ActorSystem::shutdown_ function. As I can see, this happens from time to time.

@leenozara I will double-check (almost sure, I observed this behavior) and create an example. In case I will not be able to make it (my error) - I will close...

Here is the code example: ```rust use std::time::Duration; use riker::actors::*; #[derive(Default)] struct MyActor; impl Actor for MyActor { type Msg = i32; fn recv(&mut self, ctx: &Context, msg: Self::Msg, _sender:...