std::experimental::barrier::arrive_and_drop

 

C++

Language

Standard library headers

Concepts

Utilities library

Strings library

Containers library

Algorithms library

Iterators library

Numerics library

Input/output library

Localizations library

Regular expressions library (C++11)

Atomic operations library (C++11)

Thread support library (C++11)

Filesystem library (C++17)

Technical Specifications

 

Technical specifications

Filesystem library (filesystem TS)

Library fundamentals (library fundamentals TS)

Library fundamentals 2 (library fundamentals 2 TS)

Extensions for parallelism (parallelism TS)

Extensions for concurrency (concurrency TS)

Concepts (concepts TS)

Ranges (ranges TS)

Special mathematical functions (special math TR)

 

Extensions for concurrency

std::future extensions

experimental::future

experimental::shared_future

experimental::when_all

experimental::when_any

experimental::make_ready_future

experimental::make_exceptional_future

Latches and barriers

experimental::latch

experimental::barrier

experimental::flex_barrier

Atomic smart pointers

experimental::atomic_shared_ptr

experimental::atomic_weak_ptr

 

std::experimental::barrier

barrier::barrier

barrier::~barrier

barrier::arrive_and_wait

barrier::arrive_and_drop

 

void arrive_and_drop();		(concurrency TS)

Arrive at the 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.

The behavior is undefined if the calling thread is not in the set of participating threads of this barrier.

Calls to arrive_and_drop synchronizes with the start of the completion phase of the 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.

Exceptions

Throws nothing.

Notes

If every participating thread calls arrive_and_drop(), the barrier can only be destroyed.

After a thread calls arrive_and_drop() on a barrier, it is no longer a member of its set of participating threads and hence can no longer call either arrive_and_drop() or arrive_and_wait() on the same barrier.

See also

arrive_and_wait

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