# std::barrier<CompletionFunction>::wait

> C++ Atlas: `cppatlas.com/w/cpp/thread/barrier/wait` | Source: https://en.cppreference.com/w/cpp/thread/barrier/wait | Domain: Concurrency support | Standards: C++20

If arrival is associated with the phase synchronization point for the current phase of *this, blocks at the synchronization point associated with arrival until the phase completion step of the synchronization point's phase is run.

## Official Specification Summary (cppreference)

```cpp
void wait( arrival_token&& arrival ) const; // (since C++20)
```

If `arrival` is associated with the phase synchronization point for the current phase of `*this`, blocks at the synchronization point associated with `arrival` until the phase completion step of the synchronization point's phase is run.

Otherwise, if `arrival` is associated with the phase synchronization point for the immediately preceding phase of `*this`, returns immediately.

Otherwise, i.e. if `arrival` is associated with the phase synchronization point for an earlier phase of `*this` or any phase of a barrier object other than `*this`, the behavior is undefined.

### Parameters

- `arrival` - an `arrival_token` obtained by a previous call to `arrive` on the same `barrier`

### Return value

(none)

### Exceptions

Throws `std::system_error` with an error code allowed for mutex types on error.

### Example

> Note: This section is incomplete Reason: no example

### See also

- [`arrive`](https://en.cppreference.com/w/cpp/thread/barrier/arrive): arrives at barrier and decrements the expected count (public member function)

---
Attribution: content from https://en.cppreference.com/w/cpp/thread/barrier/wait (cppreference.com), licensed under CC-BY-SA 3.0 and GFDL. Modified: converted to markdown, study notes added. Offline snapshot of 9 February 2025.