__gnu_pbds::null_type(3)

🌸 NAME 🌸

__gnu_pbds::null_type — the little guy that means no type, or the absence of type, for doing template tricks 💅

---

✨ SYNOPSIS ✨

#include <tag_and_trait.hpp>

Inherited by (okay so this is a LOT of inheritors, buckle up bestie):

__gnu_pbds::null_node_update< node_const_iterator, node_iterator, Cmp_Fn, _Alloc > *, __gnu_pbds::null_node_update< node_const_iterator, node_iterator, _ATraits, _Alloc > *, __gnu_pbds::null_node_update< node_const_iterator, node_const_iterator, _ATraits, _Alloc > *, __gnu_pbds::null_node_update< __it_type, __it_type, Cmp_Fn, _Alloc >, and __gnu_pbds::null_node_update< _Tp1, _Tp2, _Tp3, _Tp4 >.

---

🦋 Detailed Description 🦋

Represents no type, or absence of type, for template tricks. That's the whole vibe. It's the "nope, nothing here, no type, moving on" type. 🫶

And the way it shows up in so many policies — it's giving main character energy fr fr:

• In a mapped-policy, it says the associative container is actually a set. No values, just keys, iconic behavior honestly.
• In a list-update policy, it says each link does not need metadata. Zero notes. Clean. Minimal.
• In a hash policy, it says the combining hash function is actually a ranged hash function.
• In a probe policy, it says the combining probe function is actually a ranged probe function.

No cap: it's the same null_type doing all four jobs. One type, four contexts, absolutely ate. 🔥

---

👑 Author 👑

Generated automatically by Doxygen for libstdc++ from the source code. The bot wrote it, not me, I'm just the messenger bestie 💀

---

Okay that's the whole page!! This lil manual page lives in the libstdc++ manual (you can see it stamped right at the top and bottom of the original, along with the page name __gnu_pbds::null_type(3)) 🎀 Thanks for reading, ily, go template something cute 🌈💖✨