std::chrono...me_zone_link(3)

πŸ“¦ version 2024.07.05, in nixpkgs unstable, opensuse-leap 16.0

🌸 NAME 🌸

hey bestie, welcome to the C++ Standard Libary manual page for std::chrono::time_zone_link β€” and yes, the name is literally std::chrono::time_zone_link again. It's giving "I contain multitudes," but make it a chrono type. πŸ’…

✨ Synopsis ✨

Defined in header <chrono>, bestie:

class time_zone_link;       (since C++20)

okay so time_zone_link represents an alternative name for a time zone. That's the whole vibe: it's a nickname for a zone. πŸ¦‹

Users cannot construct time_zone_link objects. Nope β€” the library implementation creates time_zone_link objects when it initializes the time zone database, and it provides const access to these objects. So you get to look, not touch. πŸ‘€

time_zone_link is not copyable, but it does have a defaulted move constructor and a defaulted move assignment operator. However β€” and this is the important part, bestie β€” as users have only const access to time_zone_link objects, these functions cannot be called in user code without invoking undefined behavior.

🚨 Undefined behavior is not a slay. Do not call those move functions in your own code. Periodt.

🧚 Member functions 🧚

  • name β€” accesses the name and target of this time_zone_link.
  • target β€” public member function.

🌈 Nonmember functions 🌈

  • operator== β€” compares two time_zone_link objects.
  • operator<=> β€” function, since C++20.

xoxo, bestie πŸ’– this page came from http://cppreference.com, dated 2024.06.10, and it's the std::chrono...me_zone_link(3) manual page. mwah 🫢

πŸ“¦ where this page comes from