@cheatfate, Wonderful! Not just a new feature, but also a fix for a dangerous bug.
Independent of that, I have found that create/destroy of threads is very fast (on OSX). So araq's idea of relying of thread destruction for fast memory clean-up works beautifully. (Large memory allocation is still expensive, but that's a separate issue, possibly just the cost of bzero.) Another question: When a thread ends (for later re-spawning) in the threadpool, will it now have its heap quickly-cleaned, as for thread destruction? Alternatively, are threadvars persistent across spawns of the same thread (by chance) in a threadpool?
