std::experi...o_deallocate(3)

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

πŸ’– std::experi...o_deallocate(3) πŸ’–

okay so this page is from the C++ Standard Libary manual β€” yes, Libary, we are keeping that exactly as it appears, no autocorrect energy here 😌 β€” and it’s all about std::experimental::pmr::synchronized_pool_resource::do_deallocate. Niche? Absolutely. Iconic? Also yes. 🫢

✨ NAME ✨

std::experimental::pmr::synchronized_pool_resource::do_deallocate β€” std::experimental::pmr::synchronized_pool_resource::do_deallocate

πŸ“œ Synopsis πŸ“œ

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

okay so the way this works: this virtual function returns the memory at p to the pool. It is unspecified if or under what circumstances this operation will result in a call to deallocate() on the upstream memory resource. That’s the whole vibe β€” maybe upstream gets called, maybe not, and the spec is not committing. πŸ™ˆ

πŸ’€ Exceptions πŸ’€

Throws nothing. Not a single one. Slay. ✨

πŸ‘€ See also πŸ‘€

  • deallocate β€” deallocates memory (public member function of std::experimental::pmr::memory_resource)
  • do_deallocate β€” deallocates memory [virtual] (virtual protected member function of std::experimental::pmr::memory_resource)

🏷️ Category 🏷️

  • Noindexed pages

mwah πŸ’‹ this cutie is sourced from http://cppreference.com, version/date 2024.06.10, and it lives under std::experi...o_deallocate(3). bye bestie, go deallocate responsibly πŸ«ΆπŸŽ€

πŸ“¦ where this page comes from