std::experi...o_deallocate(3)

💅 NAME 💅

std::experimental::pmr::unsynchronized_pool_resource::do_deallocate — and yes bestie, the whole name is literally just std::experimental::pmr::unsynchronized_pool_resource::do_deallocate again, no cap, that's the entire name, we love a self-titled icon 👑

This is the C++ Standard Library, library fundamentals TS edition, and it's a virtual protected member function doing the quiet behind-the-scenes work. Lowkey main character energy, highkey a background process 🫶

✨ Synopsis ✨

virtual void do_deallocate( void* p, std::size_t bytes,
                            std::size_t alignment );

(library fundamentals TS) ⭐

So what's it doing? Okay so — it returns the memory at p to the pool. That's the vibe. Slow it down:

• p — the pointer, the memory getting handed back 🎀
• bytes — how many bytes
• alignment — the alignment

And here's the tea 🍓: it is unspecified if, or under what circumstances, this operation will result in a call to deallocate() on the upstream memory resource. So like… maybe it does, maybe it doesn't, nobody's promising anything. Don't @ it. 🙈

🌸 Exceptions 🌸

Throws nothing. Zero. Zilch. Not a single throw. It ate and left no crumbs 😌

🦋 See also 🦋

• deallocate — deallocates memory — public member function of std::experimental::pmr::memory_resource 💜
• do_deallocate [virtual] — deallocates memory — virtual protected member function of std::experimental::pmr::memory_resource 💜

🧚 Category 🧚

• Noindexed pages — it's giving mysterious, it's giving unlisted 👀 iykyk

Okay bestie, quick recap so you don't forget: hand the memory at p back to the pool, it throws absolutely nothing, and whether it ever pings the upstream memory resource's deallocate() is unspecified — so don't go assuming, fr fr. 💖

✨ That's the whole page, slay! ✨

Source and version: http://cppreference.com · <purple>2024.06.10</purple> · and the footer, of course, reads std::experi...o_deallocate(3) 🎀 Bye bestie, go deallocate responsibly 💅🔥