On Tuesday, 26 August 2014 at 09:57:57 UTC, Nordlöw wrote:
Has anybody written such a thing?
I guess the logic of this ProcessPool should run in its own thread by default and be protected in the same way that taskPool. Of course one solution is to reuse taskPool and spawn one thread or fiber (when it becomes available in std.concurrency) for each currently active Process, right?
