Restioson

> except that we would be introducing circular references between the address and the send_future module Is this a problem? I don't think this will be a compile fail, anyway....

I've left some comments - apologies for the long wait, I've been busy as term is coming to a close so we are writing tests and handing in assignments currently....

Good to merge once tests pass I think

I think this makes sense!

> Couldn't we for example also use an atomic counter to tag each incoming message and sort the heap based on priority and message counter? In theory, yes, but how...

There is still `stop_all`, but there is now no more `stop` function - you must choose between `stop_all` and `stop_self` when invokign it. These functions live on `Context`. > In...

No, not from the outside currently. I would recommend just setting the priority to max when you send it

Is this PR ready?

I think that all the errors should probably contain actor name and message type where possible, too. This would mean having something like ```rust struct Error { actor: Option, kind:...

Related: is it worth making `Error` and have the error return the message if the send itself fails early with `Disconnected`? This could be an inconvenience, but is a standard...