std::experi...re::is_ready(3)

💅 std::experi...re::is_ready(3) 💅

okay so bestie, welcome to the manual page for std::experi...re::is_ready(3) from the C++ Standard Libary — yes, that spelling is literally what's on the header, iykyk. this one is short and sweet, but we're keeping every crumb. 🍓

✨ NAME ✨

std::experimental::future::is_ready -
std::experimental::future::is_ready

it's giving "same name, same name" energy: the NAME section lists std::experimental::future::is_ready and then std::experimental::future::is_ready again. periodt. 💅

✨ Synopsis ✨

bool is_ready() const;

this is the whole flex: is_ready() checks if the associated shared state is ready. that's the vibe check. ✅

⚠️ important, no cap: the behavior is undefined if valid() is false. so please don't call it when the future isn't valid, bestie — undefined behavior is not cute. 😭💀

✨ Parameters ✨

(none) — literally no parameters. not a single one. 🫶

✨ Return value ✨

it returns true if the associated shared state is ready, otherwise false. simple as that. 🌸

✨ Example ✨

This section is incomplete
Reason: no example

yeah, the example section is incomplete and the reason is no example. no example era, I guess. 🙈

✨ See also ✨

• valid — checks if the future has a shared state, and it's a public member function of std::future<T>. slay for cross-referencing. 🔥

✨ Category ✨

* Todo no example

the category is literally * Todo no example. iconic todo energy. 🎀

mwah 💋 this page came from http://cppreference.com, with the date/version 2024.06.10, and the footer label is std::experi...re::is_ready(3). that's the whole thing, byeee 🫶✨