// Helper type to create a function-local static variable of type `T` when `T` // has a non-trivial destructor. Storing a `T` in a `base::NoDestructor<T>` will // prevent `~T()` from running, even when the variable goes out of scope. // // Useful when a variable has static storage duration but its type has a // non-trivial destructor. Chromium bans global constructors and destructors: // using a function-local static variable prevents the former, while using // `base::NoDestructor<T>` prevents the latter. // // ## Caveats // // - Must only be used as a function-local static variable. Declaring a global // variable of type `base::NoDestructor<T>` will still generate a global // constructor; declaring a local or member variable will lead to memory leaks // or other surprising and undesirable behaviour. // // - If the data is rarely used, consider creating it on demand rather than // caching it for the lifetime of the program. Though `base::NoDestructor<T>` // does not heap allocate, the compiler still reserves space in bss for // storing `T`, which costs memory at runtime. // // - If `T` is trivially destructible, do not use `base::NoDestructor<T>`: // // const uint64_t GetUnstableSessionSeed() { // // No need to use `base::NoDestructor<T>` as `uint64_t` is trivially // // destructible and does not require a global destructor. // static const uint64_t kSessionSeed = base::RandUint64(); // return kSessionSeed; // } // // ## Example Usage // // const std::string& GetDefaultText() { // // Required since `static const std::string` requires a global destructor. // static const base::NoDestructor<std::string> s("Hello world!"); // return *s; // } // // More complex initialization using a lambda: // // const std::string& GetRandomNonce() { // // `nonce` is initialized with random data the first time this function is // // called, but its value is fixed thereafter. // static const base::NoDestructor<std::string> nonce([] { // std::string s(16); // crypto::RandString(s.data(), s.size()); // return s; // }()); // return *nonce; // } // // ## Thread safety // // Initialisation of function-local static variables is thread-safe since C++11. // The standard guarantees that: // // - function-local static variables will be initialised the first time // execution passes through the declaration. // // - if another thread's execution concurrently passes through the declaration // in the middle of initialisation, that thread will wait for the in-progress // initialisation to complete. template <typename T> class NoDestructor {
public:
static_assert(
!std::is_trivially_destructible_v<T>, "T is trivially destructible; please use a function-local static " "of type T directly instead");
// Not constexpr; just write static constexpr T x = ...; if the value should // be a constexpr. template <typename... Args> explicit NoDestructor(Args&&... args) { new (storage_) T(std::forward<Args>(args)...);
}
// Allows copy and move construction of the contained type, to allow // construction from an initializer list, e.g. for std::vector. explicit NoDestructor(const T& x) { new (storage_) T(x); } explicit NoDestructor(T&& x) { new (storage_) T(std::move(x)); }
#ifdefined(LEAK_SANITIZER) // TODO(https://crbug.com/812277): This is a hack to work around the fact // that LSan doesn't seem to treat NoDestructor as a root for reachability // analysis. This means that code like this: // static base::NoDestructor<std::vector<int>> v({1, 2, 3}); // is considered a leak. Using the standard leak sanitizer annotations to // suppress leaks doesn't work: std::vector is implicitly constructed before // calling the base::NoDestructor constructor. // // Unfortunately, I haven't been able to demonstrate this issue in simpler // reproductions: until that's resolved, hold an explicit pointer to the // placement-new'd object in leak sanitizer mode to help LSan realize that // objects allocated by the contained type are still reachable.
T* storage_ptr_ = reinterpret_cast<T*>(storage_); #endif// defined(LEAK_SANITIZER)
};
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.