std::pmr::u...ool_resource(3)

πŸ“¦ version 2024.07.05, in nixpkgs unstable, opensuse-leap 16.0

πŸ’… NAME πŸ’…

std::pmr::unsynchronized_pool_resource::~unsynchronized_pool_resource β€” bestie, this is literally just the destructor. The whole page is the destructor. That's the name, that's the vibe, ok? πŸŽ€

So like, the full title is std::pmr::unsynchronized_pool_resource::~unsynchronized_pool_resource, and it lives in the C++ Standard Libary manual (yes, "Libary", that's how the manual spells it, not me πŸ’€). Come get your cleanup arc, main character energy only ✨


✨ Synopsis ✨

virtual ~unsynchronized_pool_resource();  (since C++17)
Note the virtual β€” she's a virtual destructor, since C++17, and she is not here to play. 🫢

πŸ¦‹ Description πŸ¦‹

Okay so what does she actually do? Two things. That's it. That's the whole personality:

  • Destroys an unsynchronized_pool_resource. Boom. Gone. Bye. πŸ’€
  • Deallocates all memory owned by this resource β€” and she does it by calling this->release(). So the release is doing the heavy lifting, and the destructor is just the one throwing the party. πŸ”₯

Literally no cap: everything this resource owns gets freed, and the mechanism is this->release(). That's the tea. πŸ“


πŸ‘‘ See also πŸ‘‘

  • release β€” release all allocated memory (public member function). The icon that actually frees the stuff, iykyk πŸ’œ

and that's the whole page, bestie β€” short, sweet, and fully deallocated 🌈

Source: http://cppreference.com, dated 2024.06.10, from the std::pmr::u...ool_resource(3) page. Mwah, drink water, and don't leak memory πŸ’–πŸŽ€βœ¨

πŸ“¦ where this page comes from