std::experi...ve_and_drop(3)

💅 NAME 💅

std::experimental::flex_barrier::arrive_and_drop — the flex_barrier member that says “i’m here, and also i’m leaving the group chat” 🫶

Ok so this is the std::experi...ve_and_drop(3) page from the C++ Standard Library manual, bestie. ✨

🎀 Synopsis 🎀

void arrive_and_drop();  (concurrency TS)

You arrive at the flex_barrier’s synchronization point and remove the current thread from the set of participating threads. 💅

It is unspecified whether this function blocks until the completion phase has ended. If the function blocks, the calling thread may be chosen to execute the completion phase. 😭

🚨 The behavior is undefined if the calling thread is not in the set of participating threads of this flex_barrier. Not a vibe. Do not do that.

Calls to arrive_and_drop synchronizes with the start of the completion phase of the flex_barrier. If the call blocks, then the completion of the completion phase synchronizes with the return from the call. ⭐

Calls to arrive_and_drop and arrive_and_wait never introduce data races with themselves or each other. periodt. 🔥

🌸 Exceptions 🌸

Throws nothing. literally nothing. 💀

🦋 Notes 🦋

The completion phase will be executed even if every participating thread calls arrive_and_drop. 👑

After a thread calls arrive_and_drop on a flex_barrier, it cannot call any member function on that barrier except for the destructor, even if the function object invoked by the completion phase returns a positive value. 🙈 That barrier is done with that thread, iykyk.

👑 See also 👑

• arrive_and_wait — arrive at the synchronization point and block (public member function)

Source/version/date sign-off: this page came from http://cppreference.com, version/date 2024.06.10, and the page name is std::experi...ve_and_drop(3). Bye bestie, go synchronize responsibly 💖🎀🦋