std::future...future_error(3)

💖 NAME 💖

okay so bestie, this is the std::future...future_error(3) page from the C++ Standard Libary — specifically all about std::future_error::future_error, the constructor for std::future_error. it’s giving “small error object, very important job” energy. 💅✨

🌸 Synopsis 🌸

future_error( const future_error& other ) noexcept; (1) (since C++11)
explicit future_error( std::future_errc ec );       (2) (since C++17)

two constructors, two eras, one little error type. keep your eyes on the version tags, bestie:

1. future_error( const future_error& other ) noexcept; (1) (since C++11) — the copy constructor. it initializes the contents of the new future_error object with those of other. if *this and other both have dynamic type std::future_error, then std::strcmp(what(), other.what()) == 0. no cap, that’s the whole vibe. 🫶
2. explicit future_error( std::future_errc ec ); (2) (since C++17) — constructs a new future_error object containing the error code std::make_error_code(ec). iconic behavior, honestly. ✨

🎀 Parameters 🎀

• other — another future_error object to copy. literally the one getting copied. 💖
• ec — error code. the little error-code moment. 🍓

🐚 Notes 🐚

💀 real talk: there is no standard-compliant way for the user to construct a future_error other than copying from another future_error prior to C++17.

C++11 and C++14 depict an exposition-only public constructor taking a std::error_code, and some implementations provide such a constructor. so yeah — not standard, but sometimes it’s out there living its truth. 🙈✨

mwah 💋 this little manpage came from http://cppreference.com, the 2024.06.10 version/date situation, and it’s the std::future...future_error(3) page. byeee 🫶🌈