[MLton] Multicore CPU's and MLton

[Stephen Weeks]

> I think the bottom line is: don't reject the idea of a concurrent
> collector just because it would be slow: if a design calls for part
> of the application to be concurrent with shared memory and this
> needs locking, why should a concurrent collector be slower than a
> manual way of doing that? And even if it is, couldn't it be a lot
> more reliable and easy to work with than manual memory management?

Makes sense.  Thanks for the post.