__GNU_CXX::__DETAIL::__MINI_VECTOR(3)

💖 NAME 💖

__gnu_cxx::__detail::__mini_vector< _Tp > — okay so bestie, this is __mini_vector<>, and it's literally just a stripped down version of the full-fledged std::vector<>. That's it, that's the whole vibe. It lives in the libstdc++ manual (that's the manual name up in the header, iykyk) 🦋

---

✨ SYNOPSIS ✨

#include <bitmap_allocator.h>

🎀 Public Types 🎀

• typedef const _Tp & const_reference — a const ref to a _Tp, iconic
• typedef std::ptrdiff_t difference_type — the difference type, slaying as always
• typedef pointer iterator — plot twist: the iterator is the pointer
• typedef _Tp * pointer — literally just a _Tp *, no cap
• typedef _Tp & reference — a reference to a _Tp 💅
• typedef std::size_t size_type — std::size_t, the size type of the century
• typedef _Tp value_type — _Tp is the value type, periodt

🌸 Public Member Functions 🌸

• reference back () const throw () — hands you the last element
• iterator begin () const throw () — the start of the vibe
• void clear () throw () — wipes it, no thoughts head empty
• iterator end () const throw () — the end, bestie, that's the boundary
• void erase (iterator __pos) throw () — yeets whatever's at __pos
• void insert (iterator __pos, const_reference __x) — drops __x in at __pos
• reference operator[] (const size_type __pos) const throw () — index access, subscript girlie
• void pop_back () throw () — bye bye last element 👋
• void push_back (const_reference __x) — heyyy new element at the back
• size_type size () const throw () — how many things are in here

---

🌈 Detailed Description 🌈

template<typename _Tp>
class __gnu_cxx::__detail::__mini_vector< _Tp >

__mini_vector<> is a stripped down version of the full-fledged std::vector<>.

🚨 REAL TALK: it is to be used only for built-in types or PODs. Do not come in here with your fancy objects, bestie, this is not that kind of party.

The notable differences are giving:

1. Not all accessor functions are present. Like, some of them simply did not show up. 💀
2. Used ONLY for PODs. Only PODs. PODs only. That's the whole rule. 🙈
3. No Allocator template argument. Nope, none. It uses operator new() to get memory, and operator delete() to free it. Caveat: the dtor does NOT free the memory allocated, so this is a memory-leaking vector! 😭 It's giving leaky faucet energy fr fr. So keep an eye on it.

---

👑 Author 👑

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

---

okay that's the whole page bestie, go forth and vector 💖

source: libstdc++ — this cutie came out of the libstdc++ manual, __gnu_cxx:...ctor< _Tp >(3), section 3 of the Library Functions Manual. mwah, love u, bye 🫶