On Thu, Feb 9, 2012 at 12:53 PM, Mark Roos wrote:
> For code changes I don't know. Waiting for all threads to finish seems
> problematic. When developing
> this is probably OK but I use code changes in production to hot update
> systems and to add features
> on the fly.
At some point you have t
> From: Charles Oliver Nutter
> As above, volatility is not important if threads are actively
> guarding. It only becomes a problem if you expect threads to reflect
> call site changes automatically without doing any of their own guard
> logic
My question is if I do not do a sync operation when d
