std::stop_s...top_possible(3)

hey bestie!! welcome to the std::stop_source::stop_possible(3) page from the C++ Standard Libary manual — the header title is literally std::stop_s...top_possible(3), so yes, we’re doing the truncated-name thing today ✨💖

🌸 NAME 🌸

std::stop_source::stop_possible — and one more time for the people in the back: std::stop_source::stop_possible. That’s the whole NAME, bestie. Slay.

✨ Synopsis ✨

[[nodiscard]] bool stop_possible() const noexcept;  (since C++20)

So this is the stop_possible() member function, it’s [[nodiscard]], it’s const, it’s noexcept, and it’s been around since C++20. The signature is giving “short, sweet, and absolutely not here to play.” 🎀

🎀 Parameters 🎀

(none) — literally zero parameters. Not a single one. Nothing to pass. The parameter list is empty and living its best life 💅

🔥 Return value 🔥

• Returns true if the stop_source object has a stop-state.
• Otherwise returns false.

That’s it. Boolean behavior. No cap.

💅 Notes 💅

If the stop_source object has a stop-state and a stop request has already been made, this function still returns true.

So yeah — even after a stop request has already been made, stop_possible() stays like “yup, still possible.” Not me being surprised, that’s just the documented behavior, bestie 🫶

🦋 Example 🦋

This section is incomplete.

Reason: no example.

😭 The example section is literally incomplete. There is no example. We are in our no-example era. That’s the whole note — no invented code, no fake demo, just the documented incompleteness.

🍓 Category: 🍓

• * Todo no example

Okay bye bestie — source: http://cppreference.com, version/date: 2024.06.10, page: std::stop_s...top_possible(3) 💖🌈