std::chrono::tzdb_list(3cxx)
π NAME π
std::chrono::tzdb_list β okay bestie, welcome to the std::chrono::tzdb_list(3cxx) manual page from libstdc++. This is the whole vibe for the list of chrono::tzdb objects. π
β¨ SYNOPSIS β¨
#include <chrono>
π Classes π
class const_iteratorβ the one class listed here, and yes itβs exactly this.
πΈ Public Member Functions πΈ
tzdb_list (const tzdb_list &)=deleteβ yep, this exact signature is marked=delete.const_iterator begin () const noexceptβ thebeginiterator, withnoexcept.const_iterator cbegin () const noexceptβ thecbeginiterator, withnoexcept.const_iterator cend () const noexceptβ thecenditerator, withnoexcept.const_iterator end () const noexceptβ theenditerator, withnoexcept.const_iterator erase_after (const_iterator __p)β erase-after, takes aconst_iterator __p; full tea is below.const tzdb & front () const noexceptβ front access, returnsconst tzdb &, withnoexcept.tzdb_list & operator= (const tzdb_list &)=deleteβ assignment is deleted, periodt.
π¦ Friends π¦
const tzdb & get_tzdb ()β friend.tzdb_list & get_tzdb_list ()β friend.class leap_secondβ friend class.const tzdb & reload_tzdb ()β friend.struct time_zone::_Implβ friend struct.class time_zone_linkβ friend class.struct tzdbβ friend struct.
π DETAILED DESCRIPTION π
Itβs the list of chrono::tzdb objects. Exactly that. A single object of this type is constructed by the C++ runtime, and you can access it by calling chrono::get_tzdb_list().
The front of the list is the current tzdb object, and you can get to it via chrono::get_tzdb_list().front() or chrono::get_tzdb() or *chronoget_tzdb_list().begin(). Iykyk. π¦
The chrono::reload_tzdb() function will check for a newer version and if found, insert it at the front of the list. Newer tzdb sliding into the front? Slay. β¨
Since β C++20.
π MEMBER FUNCTION DOCUMENTATION π
π const_iterator std::chrono::tzdb_list::erase_after (const_iterator __p) π
This one removes the tzdb object after the one the iterator refers to. π
Calling this function concurrently with any of front(), begin(), or end() does not cause a data race, but in general this function is not thread-safe. The behaviour may be undefined if erasing an element from the list while another thread is calling the same function, or incrementing an iterator into the list, or accessing the element being erased (unless it is accessed through an iterator).
β οΈ Thread-safety tea, bestie: no data race when called concurrently withfront(),begin(), orend(), but in general this function is not thread-safe. Undefined behaviour may happen in those listed cases, so donβt treat it like a free-for-all. π
Parameters β __p: A dereferenceable iterator.
Returns β An iterator to the element after the one that was erased (or end() if there is no such element).
Since β C++20.
πΈ const tzdb & std::chrono::tzdb_list::front () const [noexcept] πΈ
Access the current tzdb at the front of the list. This returns a reference to the same object as chrono::get_tzdb().
Returns β A reference to the current tzdb object.
Since β C++20.
π AUTHOR π
Generated automatically by Doxygen for libstdc++ from the source code.
Source/version: libstdc++. Page: std::chrono::tzdb_list(3cxx). Date: not listed in this footer, so no fake date, periodt. Thatβs the cute sign-off, bestie β mwah, and go enjoy those tzdb vibes. πβ¨π«Ά
π¦ where this page comes from
- ubuntu noble: libstdc++-14-doc 14-20240412-0ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms