I think it's too early right now, it really is a handful of lines of code; but I probably will if there is enough interest.
RIght now, actors run on a thread pool (not Nim's _threadpool_) that can be configured. The execution strategy and migration of an actor across threads is pretty dumb, but it's pluggable. Any contribution in this regard would be welcome. My idea (not implemented right now) is to keep actors on the same thread unless some condition is not met (to limit copying). Messaging uses channels.
