On Saturday, 23 August 2014 at 23:46:43 UTC, Mike wrote:
One quote from the FAQ:
"Nimrod primarily focuses on thread local (and garbage
collected) heaps and asynchronous message passing between
threads. Each thread has its own GC, so no "stop the world"
mechanism is necessary. An unsafe shared memory heap is also
provided.
Do you have an idea, how Nimrod shares memory? Thread-local GCs
mean the memory should be deep copied between threads, which is
not always a good idea, e.g. when you receive a big complex data
structure from network in one thread and pass it to the main
thread.
