run a func in its own, separate thread - don't wait for result
fork one thread per element, each running the func
fork a bunch of threads, then join them and return the results
fork a bunch of threads, then join them and return the results...all within a timeout.
fork a bunch of threads, then join them and return the results...all within a timeout. The return should have an element for each input that finished in time...
join a bunch of thread - this is more to have a symmetry for fork
make a promise and start it in the background
just repeat the func on as many threads
repeat the func on as many threads, but each has a result which is joined and then collected
repeat the func on as many threads, but each has a result which is joined and then collected
is passed the thread number, for no good reason :)
same as forkForeach, but use the given number of threads and slice the iterable
multithreading helpers, to tie me over until I learn to effectively exploit actors or other inferior beings