On Monday, 6 January 2020 08:36:56 UTC, ffm...@web.de wrote: > > in Amoeba a thread can be suspended, thereafter be sent to some other > machine where it is resumed. >
Thread migration doesn't solve the OP's issue, because threads share memory with other threads: passing a copy of something is not the same as passing a pointer to something, unless you have a way for writes through a pointer to act on the original memory. Ruby has(*) something like this in DRb. If you pass an object over DRb, then at the far end a proxy object is constructed, so that method calls on that object are relayed back to the original host. Systems with immutable values / pass-by-value only (e.g. Erlang) avoid this issue, since it doesn't matter whether you have a reference to a copy or the the original. Regards, Brian. (*) or had: it's many years since I used Ruby in anger. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/9d358b31-ddf4-4548-af1e-cb0e42d25573%40googlegroups.com.
