std::chrono...:erase_after(3)

💅 NAME 💅

std::chrono::tzdb_list::erase_after — yes bestie, it's literally the same name twice, that's just how cppreference rolls, don't @ me 🎀 (this one lives in the C++ Standard Library, mwah)

✨ Synopsis ✨

const_iterator erase_after( const_iterator p );  (since C++20)

okay so what this icon does: it erases the std::chrono::tzdb that's referred to by the iterator following p. like, p itself is safe, it's the next one that gets yeeted 🫶

⚠️ heads up bestie — the behavior is undefined if that iterator is not dereferenceable. not "kinda weird", not "probably fine", undefined. do a vibe check on your iterator before you send it, fr fr 💀

and the good news? no pointers, references, or iterators are invalidated except for the ones referring to the erased element. everything else stays valid, slay ✨

🌸 Return value 🌸

An iterator pointing to the element following the erased element 💖 …or end() if no such element exists. either way you get a thing back, no cap 🌈

🦋 Notes 🦋

• tzdb_list is intended to be implementable as a singly linked list, and its interface resembles that of std::forward_list. the family resemblance is real 👑
• but here's the catch: it has no before_begin(). 😭
• and because of that, it is not possible to erase the first element. the first one is main character energy and simply cannot be removed, periodt 💅

that's the whole page, you ate that 💜✨ source/version cppreference.com, dated 2024.06.10 — go forth and erase responsibly, bestie 🧚🍓