std::unorde...ed_multimap(3)

🎀 NAME 🎀

Okay bestie, this is the std::unorde...ed_multimap(3) page from the C++ Standard Libary (yes, that's the header's spelling, I'm not fixing it 💀). The name is std::unordered_multimap::~unordered_multimap — and the NAME line after the dash is also std::unordered_multimap::~unordered_multimap. It's giving "this destructor knows exactly who she is." 💅

✨ Synopsis ✨

~unordered_multimap();  (since C++11)

So the destructor signature is ~unordered_multimap();, and it's been a thing since C++11 ✨.

What it does, fr fr: it destructs the unordered_multimap. The destructors of the elements are called, and the used storage is deallocated. That's the whole main-character move. 👑

⚠️ Important caveat, bestie: if the elements are pointers, the pointed-to objects are not destroyed. The container is cleaning up its own storage and calling element destructors, not chasing down whatever your pointers point at. No cap. 🙈

🌸 Complexity 🌸

Linear in the size of the unordered_multimap. That's the complexity, periodt. ⭐

That's the whole page, bestie 🫶 — source is http://cppreference.com, dated 2024.06.10. Go forth and destruct responsibly. 💖🔥