Thomas de Zeeuw

This is because `:user` in the first route is a wild card, which match `gordon/:profile` of the second route as well. See #175.

This commit https://github.com/golang/go/commit/874a605af0764a8f340c3de65406963f514e21bc, might be of interest. But this in only after 1.5 is released.

Some more design ideas. An updated version of the trait: ```rust pub trait VirtualActor { type Message; type Actor: Actor; type Error; type RuntimeAccess; /// Create a new actor that...

```diff diff --git a/src/actor/mod.rs b/src/actor/mod.rs index 464e722..73931e0 100644 --- a/src/actor/mod.rs +++ b/src/actor/mod.rs @@ -144,9 +144,12 @@ mod sync; #[cfg(test)] mod tests; +mod r#virtual; #[doc(inline)] pub use context::{Context, NoMessages, ReceiveMessage, RecvError};...

> Any progress on virtual actors? I like its design concept very much I'm afraid not.

Main hurdle is the `never_type` feature: https://github.com/rust-lang/rust/issues/35121. Could use `std::convert::Infallible` in the mean time.

Do the same for `spawn_sync_actor` from https://github.com/Thomasdezeeuw/heph/pull/541.

Could use the recently stabilised `thread::JoinHandle::is_finished` for the control of the sync actor.

Also add an option to `ActorFuture`, maybe an additional creation option?

Needed: - [ ] (de)serialisation of messages #214. - [x] Machine actors #213. - [ ] How to connect to peers? - [ ] How to connect to a remote...