std::type_info(3)

🦋 std::type_info 💅

okay bestie, welcome to the Library Functions Manual, section 3 — today's main character is std::type_info, and she's literally the blueprint. 🎀

---

✨ NAME ✨

std::type_info — she's Part of RTTI. that's the whole vibe. 👑

---

✨ SYNOPSIS ✨

#include <typeinfo>

🌸 Public Member Functions 🌸

• virtual ~type_info () — the destructor, she's virtual and she's first, more on that drama below 💀
• virtual bool __do_catch (const type_info *__thr_type, void **__thr_obj, unsigned __outer) const — a virtual bool, the docs give her no solo write-up, she just exists 🫶
• virtual bool __do_upcast (const __cxxabiv1::__class_type_info *__target, void **__obj_ptr) const — another virtual bool, same deal, no individual documentation entry ✨
• virtual bool __is_function_p () const — virtual bool, no separate doc block, just vibes 💜
• virtual bool __is_pointer_p () const — same, virtual bool, undocumented individually 🦋
• bool before (const type_info &__arg) const noexcept — the ordering check, she's noexcept and she's got a whole section below 🔥
• size_t hash_code () const noexcept — returns a size_t, noexcept, no standalone write-up in the docs 😌
• const char * name () const noexcept — the famous one, noexcept, fully documented below ⭐
• constexpr bool operator== (const type_info &__arg) const noexcept — constexpr, noexcept, no individual doc entry, she just slays quietly 🌈

🧚 Protected Member Functions 🧚

• type_info (const char *__n) — protected constructor taking a const char *__n, so it's giving "not for you unless you're the implementation" 🙈

🍓 Protected Attributes 🍓

• const char * __name — a protected const char * called __name, iconic, no further notes given 💅

---

✨ Detailed Description ✨

Part of RTTI. 🫶

The type_info class describes type information generated by an implementation. that's it, that's the thesis. no cap. ✨

---

🎀 Constructor & Destructor Documentation 🎀

virtual std::type_info::~type_info () [virtual]

okay so the docs are VERY specific here and i'm obsessed: Destructor first. Being the first non-inline virtual function, this controls in which translation unit the vtable is emitted. The compiler makes use of that information to know where to emit the runtime-mandated type_info structures in the new-abi. like she's literally the anchor for vtable placement, main character energy fr fr 👑🔥

---

💖 Member Function Documentation 💖

bool std::type_info::before (const type_info & __arg) const [noexcept]

Returns true if *this precedes __arg in the implementation's collation order. that's the whole thing — implementation's collation order, not yours, not mine, hers. 💅

const char * std::type_info::name () const [inline], [noexcept]

Returns an implementation-defined byte string. 🦋

⚠️ and bestie listen — this is not portable between compilers! implementation-defined means exactly what it sounds like. do NOT hardcode comparisons against it, i'm begging 😭💀

---

⭐ Author ⭐

Generated automatically by Doxygen for libstdc++ from the source code. 🤖✨

---

and that's the page!! sign-off time: this whole thing came to you courtesy of libstdc++ and it's std::type_info(3) — go forth and RTTI responsibly, ily, bye 💜🎀🌈