Exit Zen
:308
:308
English
A constant iterator whose value type is `value_type`.
28/530 · 53
:351
:351
English
---
3/100 · 3
34
:356
English
If an operation *op* is explicitly designated as _blocking on_ `x`, where `x` is an instance of a `boost::concurrent_node_set`, prior blocking operations on `x` synchronize with *op*. So, blocking operations on the same `concurrent_node_set` execute sequentially in a multithreaded scenario.
162/2910 · 291
34
:392
English
If an operation *op* is explicitly designated as _blocking on_ `x`, where `x` is an instance of a `boost::concurrent_flat_map`, prior blocking operations on `x` synchronize with *op*. So, blocking operations on the same `concurrent_flat_map` execute sequentially in a multithreaded scenario.
146/2910 · 291
:297
:297
English
---
3/100 · 3
34
:317
English
A const_local_iterator object can be used to iterate through a single bucket.
34/770 · 77
:348
:348
English
---
3/100 · 3
:353
:353
English
---
3/100 · 3
35
:35
English
xref:reference/header_unordered_node_set.adoc[`<boost/unordered/unordered_node_set.hpp>`]
103/890 · 89
35
:122
English
xref:regular.adoc#regular_iterator_invalidation[Iterators can be invalidated by calls to insert or rehash]. +
80/1090 · 109
35
:57
English
Added efficient move construction of `boost::unordered_flat_(map|set)` from
12/750 · 75
35
:295
English
^|`boost::concurrent_flat_map` ^|`boost::unordered_flat_map`
60/600 · 60
35
:343
English
An operation is said to be _blocking on rehashing of_ ``__x__`` if it blocks on `x` only when an internal rehashing is issued.
53/1260 · 126
35
:101
English
image::benchmarks-set/gcc/scattered unsuccessful looukp.xlsx.practice non-unique 5.png[width=250,window=_blank,link=_images/benchmarks-set/gcc/scattered unsuccessful looukp.xlsx.practice non-unique 5.png]
204/2040 · 204
35
:117
English
Although the implementation internally uses SIMD technologies, such as https://en.wikipedia.org/wiki/SSE2[SSE2^] and https://en.wikipedia.org/wiki/ARM_architecture_family#Advanced_SIMD_(NEON)[Neon^], when available, this does not affect interoperatility. For instance, the behavior is the same for Visual Studio on an x64-mode Intel CPU with SSE2 and for GCC on an IBM s390x without any supported SIMD technology.
256/4130 · 413
:320
:320
English
---
3/100 · 3
35
:100
English
`max_load_factor` doesn't let you set the maximum load factor yourself, it just lets you give a _hint_. And even then, the standard doesn't actually require the container to pay much attention to this value. The only time the load factor is _required_ to be less than the maximum is following a call to `rehash`. But most implementations will try to keep the number of elements below the max load factor, and set the maximum load factor to be the same as or close to the hint - unless your hint is unreasonably small or large.
179/5260 · 526
35
:327
English
A constant iterator with the same value type, difference type and pointer and reference type as const_iterator.
48/1110 · 111
35
:413
English
An operation is said to be _blocking on rehashing of_ ``__x__`` if it blocks on `x` only when an internal rehashing is issued.
53/1260 · 126
35
:145
English
to the container. Typically, such access is in read mode (that is, concurrent) even for modifying operations, so for most practical purposes there is no thread contention at this level. Access is only in write mode (blocking) when rehashing or performing container-wide operations such as swapping or assignment.
96/3120 · 312