Restioson

Sorry, I haven't had much time to work on this because of exams... I will get back to it when they are finished though.

This sounds like a nice API! Though, as we are currently moving toward removing convenience methods to slim down the API with a view to an extension crate soon, then...

Sure, that makes sense!

Hmm, this could be interesting, but it would probably lead to explosive compile times 😅 The upshot is that it could be done in an extension crate, though.

Technically speaking, could `select`, `join`, `yield_once`, and `run` all go outside of the main crate? Where do we want to draw the line on these? Personally, I think `run` is...

I've gone ahead and added all the mentioned issues to https://github.com/Restioson/xtra/milestone/4, by the way!

I definitely agree that we should clarify these, and I agree with most of the points! > Convenient APIs over ordering-guarentees Could you give an example of when this tradeoff...

> What isn't so clear to me at the moment is the main aspects in which this project differs from other available actor frameworks. Perhaps a brief comparison to the...

Hm, I would actually tend to disagree with this change. This adds a fixed cost of `8 * capacity` bytes per each type of mailbox, even if you don't use...

If they set capacity to zero that'd affect the default priority queue too, though