> If the error goes away, then that will "prove" the HashSet (and presumably > every other complex threadvar object) needs to be initialised explicitly in > each thread. If that is the case, it would be nice to have some syntax > (something like the opposite of "static:") that takes care of that for you.
Yeah, that's how thread local storage works, every thread needs to initialize its very own memory. We had something like you propose called `onThreadCreation` but it just encourages races and so we removed it again.
