ThreadRestrictions: leak the thread local variable

base/thread_restrictions.cc

 // Copyright (c) 2010 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "base/thread_restrictions.h"
 
 // This entire file is compiled out in Release mode.
 #ifndef NDEBUG
 
 #include "base/lazy_instance.h"
 #include "base/logging.h"
 #include "base/thread_local.h"
 
 namespace {
 
-static base::LazyInstance<base::ThreadLocalBoolean>
+base::LazyInstance<base::ThreadLocalBoolean,

[willchan no longer on Chromium, 2010/10/21 20:26:50]

Why don't you just move this anonymous namespace within the base namespace, then
you can get rid of all the base:: which should make this a bit prettier.

+                   base::LeakyLazyInstanceTraits<base::ThreadLocalBoolean> >
     g_io_disallowed(base::LINKER_INITIALIZED);
 
 }  // anonymous namespace
 
 namespace base {
 
 // static
 void ThreadRestrictions::SetIOAllowed(bool allowed) {
   g_io_disallowed.Get().Set(!allowed);
 }
 
 // static
 void ThreadRestrictions::AssertIOAllowed() {
   if (g_io_disallowed.Get().Get()) {
     LOG(FATAL) <<
         "Function marked as IO-only was called from a thread that "
         "disallows IO!  If this thread really should be allowed to "
         "make IO calls, adjust the call to "
         "base::ThreadRestrictions::SetIOAllowed() in this thread's "
         "startup.";
   }
 }
 
 }  // namespace base
 
 #endif  // NDEBUG