<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 14, 2010, at 1:25 AM, John McCall wrote:</div><blockquote type="cite"><div>While I agree with Sebastian, I wonder if we care. Is there any good<br>reason to not just require the user to ensure that pass initialization<br>is thread-safe? "Don't try to concurrently initialize the standard pass<br>registry" does not seem like an unreasonable constraint.<br></div></blockquote></div><br><div>The problem is that we're trying to do lazy implicit initialization, hidden in the pass constructors. It's not unreasonable for users to be instantiating passes on different threads.</div><div><br></div><div>--Owen</div></body></html>