__GNU_PBDS::DETAIL::COND_DEALTOR(3)

✨ NAME ✨

__gnu_pbds::detail::cond_dealtor< Entry, _Alloc > — bestie, this is the conditional deallocate constructor argument. That's it, that's the whole job 💅

(also hi, you're reading the Library Functions Manual page for it, welcome 🫶)

---

🌸 SYNOPSIS 🌸

Okay so before literally anything works, you gotta pull in the header:

#include <cond_key_dtor_entry_dealtor.hpp>

💖 Public Types 💖

• typedef HT_Map::entry entry
• typedef HT_Map::entry_allocator entry_allocator
• typedef alloc_traits::allocator_type entry_allocator
• typedef alloc_traits::pointer entry_pointer
• typedef HT_Map::key_type key_type

not me noticing entry_allocator shows up twice with two different definitions… that's just how the page is, i don't make the rules 😭 both are listed, both stay.

🦋 Public Member Functions 🦋

• cond_dealtor (entry_allocator *p_a, entry *p_e) — the constructor, handing it an allocator pointer and an entry pointer.
• cond_dealtor (entry_pointer p_e) — the other constructor, just an entry pointer this time.
• void set_key_destruct () — flips on key destruction.
• void set_no_action () — vibe check: do nothing.
• void set_no_action_destructor () — no action, but the destructor kind of no-action.
• void set_no_action_destructor () — …yes bestie it's listed once, i'm just obsessed with it.

okay real talk, the actual list is: set_key_destruct (), set_no_action (), set_no_action_destructor (). three of them. that's it. slay.

🎀 Protected Attributes 🎀

• bool m_key_destruct — a little bool keeping track of the key-destruct situation.
• entry_allocator *const m_p_a — the allocator pointer, and it's const so don't even think about it 🔥
• entry *const m_p_e — the entry pointer, also const, also not up for discussion.

---

👑 Detailed Description 👑

template<typename Entry, typename _Alloc>
class __gnu_pbds::detail::cond_dealtor< Entry, _Alloc >

Conditional deallocate constructor argument.

Conditional dey destructor, cc_hash.

yeah "dey" is genuinely what it says, and "cc_hash" is genuinely what it says. i am not touching that. preserve the lore 📜

---

⭐ Author ⭐

Generated automatically by Doxygen for libstdc++ from the source code. no human wrote this, a machine did, and honestly? it ate 💅✨

---

and that's the whole page, bestie 🫶 this absolute icon lives in the libstdc++ docs — no cap, it's libstdc++, and there's no date on this footer, so the timestamp is giving mysterious 🙈💜 bye pookie, go read some headers 🎀