STD::_MAYBE_UNARY_OR_BINARY_FUNCTION(3cxx)

💖 NAME 💖

std::_Maybe_unary_or_binary_function< _Res, _ArgTypes > — bestie, this is a lil helper template from the C++ standard library, and it lives in the 3cxx manual, okurrr ✨

---

🌸 SYNOPSIS 🌸

#include <refwrap.h>

That's literally it. One include. Iconic behaviour fr fr 💅

---

🦋 Detailed Description 🦋

Okay so picture this template:

template<typename _Res, typename... _ArgTypes>
    struct std::_Maybe_unary_or_binary_function< _Res, _ArgTypes >

Not me being obsessed with a struct that literally just... decides what to inherit from 😭

Here's the vibe: it derives from unary_function or binary_function, or perhaps nothing, depending on the number of arguments provided. So like, it does a vibe check on how many _ArgTypes you handed it and then picks its ancestry accordingly. Slay 💅

And the primary template is the basis case, which derives nothing. So if you don't match a specialization, you get the base case, and the base case is giving absolutely nothing. No inheritance, no drama, just a struct standing there. Main character energy but make it empty ✨

Definition at line 53 of file refwrap.h.

---

👑 Author 👑

Generated automatically by Doxygen for libstdc++ from the source code. So technically no human wrote this page — it was birthed by a documentation generator, and honestly? It ate 🍓

---

And that's the whole page, bestie 🫶 This little cutie came to you straight from libstdc++, documented for the 3cxx manual by the Doxygen autogen machine itself — no cap, that's genuinely where it came from 💜🎀