Lines Matching defs:Singleton
5 // PLEASE READ: Do you really need a singleton?
10 // Instead of adding another singleton into the mix, try to identify either:
11 // a) An existing singleton that can manage your object's lifetime
15 // If you absolutely need a singleton, please keep them as trivial as possible
45 // Default traits for Singleton<Type>. Calls operator new and operator delete on
75 // Alternate traits for use with the Singleton<Type>. Identical to
76 // DefaultSingletonTraits except that the Singleton will not be cleaned up
87 // Alternate traits for use with the Singleton<Type>. Allocates memory
88 // for the singleton instance from a static buffer. The singleton will
93 // tracing, where the singleton instance is of a type carefully constructed to
97 // termination race on the heap-based singleton - e.g. if one thread calls
110 // WARNING: User has to deal with get() in the singleton class
144 // The Singleton<Type, Traits, DifferentiatingType> class manages a single
169 // #include "base/memory/singleton.h"
171 // return Singleton<FooClass>::get();
177 // NOTE: The method accessing Singleton<T>::get() has to be named as GetInstance
181 // creating multiple copies of the singleton.
183 // Singleton<> has no non-static members and doesn't need to actually be
193 // On every platform, if Traits::RAE is true, the singleton will be destroyed at
199 // If Traits::RAE is false, the singleton will not be freed at process exit,
200 // thus the singleton will be leaked if it is ever accessed. Traits::RAE
216 class Singleton {
218 // Classes using the Singleton<T> pattern should declare a GetInstance()
219 // method and call Singleton::get() from within that.
237 // instance_ pointer must acquire visibility over the singleton data.
277 // Calling OnExit while singleton is in use by other threads is a mistake.
279 // AtExit should only ever be register after the singleton instance was
289 base::subtle::AtomicWord Singleton<Type, Traits, DifferentiatingType>::
