STD::HAS_VIRTUAL_DESTRUCTOR(3)

💖 NAME 💖

std::has_virtual_destructor< _Tp > — okay bestie, the whole entire name is has_virtual_destructor. That's it. That's the name. No notes. 💅

---

✨ SYNOPSIS ✨

#include <type_traits>

That's the include. That's the whole include. One line, zero drama, very demure. 🎀

---

🌸 DETAILED DESCRIPTION 🌸

Okay so, here's the tea, and I need you to sit down for it:

template<typename _Tp>
    struct std::has_virtual_destructor< _Tp >"has_virtual_destructor

Yes. That's the whole description. That is literally the entire Detailed Description section, bestie. The docs said "detailed" and then handed us a template header and a struct name with a lil stray " in there like it got distracted mid-sentence. Iconic behavior, honestly. 😭

No prose. No explanation. No "returns true if…", no nothing. Just the signature, sitting there, serving absolute minimalist main character energy. 👑

Real talk though — I'm not gonna make up behavior that isn't on this page. This manual gives you the name, the header, and the declaration. If you need to know more, that's a you-and-the-standard conversation, not a me-and-this-manpage conversation. 🙈

---

🫶 AUTHOR 🫶

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

So no human author to thank. Just Doxygen, doing its lil thing, pumping out pages while we sleep. Robotic king behavior. 🤖✨

---

And that's the page, gorgeous. This one came to you from libstdc++ — the manpage itself is titled std::has_v...tor< _Tp >(3) because even the title got truncated, and honestly? Slay. 🦋 Stay curious, read your headers, and remember: short docs are still docs. Periodt. 💖🌸🎀