STD::NEGATE(3)

💅 NAME 💅

std::negate< _Tp > — bestie, it's one of the math functors. That's it, that's the whole job description. 🎀

---

✨ SYNOPSIS ✨

#include <functional>

Inherits std::unary_function< _Tp, _Tp >. Yeah babe, it's giving legacy inheritance, we love a family tree. 🌸

🫶 Public Types

• typedef _Tp argument_type — this is the type of the argument, no cap. It's literally what you feed in.
• typedef _Tp result_type — and this is the return type, aka what you get back. 🦋

💖 Public Member Functions

constexpr _Tp operator() (const _Tp &__x) const

That's the one, that's the whole move. constexpr, takes a const ref, hands you back a _Tp. Iconic behaviour. 👑

---

🔥 Detailed Description 🔥

template<typename _Tp>
struct std::negate< _Tp >

"One of the math functors." — direct quote, they said it, not me. It's a template struct, _Tp is your type parameter, and honestly? It just does its little math thing. Main character energy, lowkey. 💜

---

🌈 Member Typedef Documentation 🌈

typedef _Tp std::unary_function< _Tp, _Tp >::argument_type [inherited]

argument_type is the type of the argument. (Yes, inherited — she got it from her parent class, as one does. 🧚)

typedef _Tp std::unary_function< _Tp, _Tp >::result_type [inherited]

result_type is the return type. Same inherited situation, same slay. ⭐

Not me telling you twice that these are inherited — but fr fr, both typedefs come from std::unary_function< _Tp, _Tp >, and both are documented as inherited. Respect the lineage. 💅

---

🎀 Author 🎀

Generated automatically by Doxygen for libstdc++ from the source code. So technically no human wrote this, the machine did, and it ate. 😭

---

Okay bestie, that's the whole page, go forth and negate things (mathematically) 💖

Sign-off vibes: this came from the libstdc++ manual, page std::negate< _Tp >(3), and it's Doxygen-generated from the source code, so if anything's cursed, blame the source, not me. 🫶