My reign library basically just ports over the Erlang idea; asynch messages, PID-like things that can be transmitted across the network and identify the same mailboxes within a cluster. It's meant to be a porting aid, not a solution you'd reach for in Go to create a brand new program. (If you do that, it's on you.) Clustering like this is nontrivial and the big reason I'm sitting on the code locally until clustering is at least working under some circumstances; without clustering support, the mailboxes are just an invitation to write nonidiomatic code for no gain.
Preemptive scheduler, I doubt Go have this, then again Go doesn't have a VM/OS system.
And I believe also heap allocation... the two cases together make what is still "partial preemption" pretty damn effective.
Only for those not versed in java.util.concurrent, TPL, PPL, TBB, Cilk Plus.
But then, one can use something like Akka, which I forgot to mention, and still be on the JVM.
Select in Go only blocks if you don't feel out the "default:" case...
select {
case: foo := <-fooCh
fmt.Printf("got %v\n", foo)
default:
fmt.Println("got nothing")
}
I wouldn't be surprised by this. Go's concurrency pattern is fantastic, but to match what Erlang does it needs to be easily extended beyond the running process. Can channels connect multiple "nodes" yet? That is, two running go programs, can they communicate via channels or do they have to use some other IPC mechanism? Across a network? That universal communication structure is (IMO) erlang's killer feature.