Means to make actor calls from another thread about stakker HOT 1 OPEN

Ok I've been thinking a little bit more about this, so I'm gonna share some thoughts in case it helps in moving forward.

What I'd like the most, I think, is to have a simple unified API, with a few interrelated traits, at least one for each type at each side of one bridge, maybe one for the message type that comes through. The core issue may very well be reduced to: Messages comming from one stakker system must be dealt with by another stakker system, back and forth. The rest would be implementation details. What are the guarantees stakker wants to give and what's the minimum stakker needs to ask from the implementor? That's what needs to be clarified in the API I believe.

Also a few basic implementations should be offered, one for inter-thread communication between stakker instances, and maybe one for same-thread communication that could be handy as a base reference for benchmarks. More complex implementations could be added, and custom ones.

I also think theres gonna be a need for an error type. At the very least the api method for referring messages should return a Result with an error that probably should be as generic as possible.

In the case of stakker maybe it's worth considering creating a crate level non_exhaustive enum that includes the inter-stakker communication errors of its concrete implementations?

from stakker.