sc::type_info_key(3)

🦋 NAME 🦋

okay so, bestie, gather round, because today's main character is sc::type_info_key 💖 That's it. That's the whole name. Short, sweet, and lowkey iconic — no cap.

---

✨ SYNOPSIS ✨

Here's the full squad, the entire roster, nobody gets left out 🙈 This page lives in the Library Functions Manual, and it's giving C++ energy fr fr:

type_info_key (const std::type_info *ti)
type_info_key & operator= (const type_info_key &)
int operator== (const type_info_key &) const
int operator< (const type_info_key &) const
int cmp (const type_info_key &) const

💅 Public Member Functions 💅

These are the public ones, the ones everybody gets to see, and we are obsessed:

• type_info_key (const std::type_info *ti) — the one that shows up with a single const std::type_info *ti and nothing else. Just that pointer. Periodt. 🌸
• type_info_key & operator= (taking const type_info_key &) — the assignment moment, and the way that it hands you back a type_info_key &... it's giving return-by-reference. 🔥
• int operator== (taking const type_info_key &) — the equality one, <cyan>const</cyan> and all, and it comes back at you with an int. ⭐
• int operator< (taking const type_info_key &) — the less-than one, also <cyan>const</cyan>, also an int. Same energy, different operator. 💜
• int cmp (taking const type_info_key &) — and then there's cmp, bestie, int-returning, const-marked, standing there like it owns the place. 👑

not me listing out every single signature twice 😭 but bestie, we do not skip, we do not merge, we do not "fix" anything. every detail stays, every time. 🫶

---

👑 AUTHOR 👑

Generated automatically by Doxygen for MPQC, straight from the source code. Yep. A robot did this. Doxygen woke up, read the source, and wrote a whole manual page. Respect. 💅

---

so yeah, that's the whole page, and honestly? ate. no crumbs. 🍓

This one's from MPQC, Version 2.3.1, and you're reading sc::type_info_key(3) in the Library Functions Manual. bye bestie, go read some source code 🧚🌈