std::experi...x,begin,end(3)

💅 std::experi...x,begin,end(3) 💅

okay so you're in the C++ Standard Libary manual, bestie, and this page is the whole std::experimental::ranges::tag squad being iconic together. The NAME line is a whole mood — it lists the full roster twice, because apparently once was not enough:

std::experimental::ranges::tag::in,in1,in2,out,out1,out2,fun,min,max,begin,end

That's std::experimental::ranges::tag::in, in1, in2, out, out1, out2, fun, min, max, begin, and end. Yes, all of them. Slay. ✨

✨ Synopsis ✨

Defined in header <experimental/ranges/algorithm>:

struct in { /* implementation-defined */ };

struct in1 { /* implementation-defined */ };
struct in2 { /* implementation-defined */ };
struct out { /* implementation-defined */ };
struct out1 { /* implementation-defined */ };
struct out2 { /* implementation-defined */ };      (ranges TS)
struct fun { /* implementation-defined */ };
struct min { /* implementation-defined */ };
struct max { /* implementation-defined */ };
struct begin { /* implementation-defined */ };

struct end { /* implementation-defined */ };

These classes are TagSpecifiers for use with ranges::tagged. no cap, that's the whole vibe.

The name of a specifier is also the element name it corresponds to. For instance, ranges::tagged<std::pair<int, int>, tag::min, tag::max> provides a set of named accessors named min and a set of named accessors named max. iykyk — the tag name and the accessor name are literally matching, and that's the point. 🎀

This lil' page came from http://cppreference.com, dated 2024.06.10, and it's filed under std::experi...x,begin,end(3) — mwah, bye bestie 💖🫶