Thomas Eizinger

I certainly don't know how to fix it :)

I think that would be a big ergonomic hit as users would need to interact with that. Some of the dynamic dispatch comes from the user implementing `Handler` multiple times.

If we - by default - encourage use of a macro for the creation of handlers, this could probably be hidden from the user altogether. See https://github.com/Restioson/xtra/issues/111.

I propose to merge `ordered` and `priority` into a `unicast` mailbox. I think this can wait for after `0.6` as it doesn't affect the public API although it would be...

> Hi, sorry for getting to this so late. I am back from holiday now :) > > I think the main thing around having a unified mailbox would be...

Here are meeting "notes" from an out-of-band meeting: https://hackmd.io/@AeK4eNTZTGGJXAT4cxS_Zw/r1MvCrHCi. The conclusion of the meeting is: - We agree that the ordered & priority mailboxes should be merged: - It should...

> It would be handy for users to catch something or log, without a need of executing docker commands manually. If we add everything that is "handy", our API surface...

> My concrete use case - I needed to see container logs while running the tests. I'd accept a feature PR that explores how we can forward a container's logs...

Thank you for writing this up @endertunc ! Exposing a `dyn Read` or `dyn AsyncRead` sounds like a good approach. I'd expose them on `Container` directly though instead of going...

> +1, I would like to access container logs, my use case is that I have an error that happens only in CI but not locally. What that usecase perhaps...