* Graydon Hoare: > (2) Support *lots* of tasks. Millions. Such that a programmer has no > fear about making "too many" tasks in a system, if it decomposes > nicely. If for no other reason than support for isolation-based local > reasoning (though concurrent, or interleaved, or truly parallel > execution is also nice to exploit whenever it's surfaced this way).
This simply does not work. You cannot make tasks much cheaper than GHC thunks (except by eliminating them through compiler transformations), yet creating too much of them is often a source of disappointing performance. If you don't buy this argument, you might want to look at the Erlang pmap example. The textbook implementation looks nice on paper, but it fares poorly on larger workloads because overscheduling is a problem for Erlang, too. Or do you mean short-lived tasks, aproaching coroutines and generators? _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
