2. Boost Unordered Translation (zh_Hans)
3. English
4. Zen

10 :283
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — *Template Parameters* 21/10000 · 21
10 :254
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — _T_ 3/10000 · 3
10 :53
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — For successful (element found) or unsuccessful (not found) lookup, provides the number of operations performed by a container and statistics on the associated __probe length__ (number of xref:structures.adoc#structures_open_addressing_containers[bucket groups] accessed) and number of element comparisons per operation. 319/10000 · 319
10 :300
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — *Template Parameters* 21/10000 · 21
10 :288
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Description 11/10000 · 11
10 :237
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Description 11/10000 · 11
10 :245
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — _Hash_ 6/10000 · 6
10 :284
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Description 11/10000 · 11
11 :11
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — xref:rationale.adoc[] 21/10000 · 21
11 :70
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In a similar manner to using `reserve` for ``vector``s, it can be a good idea to call `reserve` before inserting a large number of elements. This will get the expensive rehashing out of the way and let you store iterators, safe in the knowledge that they won't be invalidated. If you are inserting `n` elements into container `x`, you could first call: 352/10000 · 352
11 :54
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — for unordered associative containers and feature one of the fastest implementations in the market within the technical constraints imposed by the required standard interface. 174/10000 · 174
11 :31
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Local iterators would be very inefficient and may not be able to 64/10000 · 64
11 :51
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — for(std::string::const_iterator it = x.begin(); it != x.end(); ++it) { boost::hash_combine(seed, std::toupper(*it, locale)); } 126/10000 · 126
11 :24
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — image::benchmarks-set/gcc/running insertion.xlsx.practice.png[width=250,link=_images/benchmarks-set/gcc/running insertion.xlsx.practice.png,window=_blank] 154/10000 · 154
11 :101
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — But, in general, visitation functions should be as lightweight as possible to reduce contention and increase parallelization. In some cases, moving heavy work outside of visitation may be beneficial: 199/10000 · 199
11 :75
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The `stats` object provides the following information: 54/10000 · 54
11 :40
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In open-addressing containers, buckets can hold at most one element; if a collision happens (like is the case of `D` in the example), the element uses some other available bucket in the vicinity of the original position. Given this simpler scenario, Boost.Unordered open-addressing containers offer a very limited API for accessing buckets. 340/10000 · 340
11 :47
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — This feature has been retained for backwards compatibility with previous versions of Boost.Unordered: users are encouraged to update their code to use `std::piecewise_construct` and ``std::tuple``s instead. 206/10000 · 206
11 :34
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — ```c++ auto const idx = get_bucket_idx(hash_function(key)); node* p = buckets[idx]; // first load node* n = p->next; // second load if (n && is_in_bucket(n, idx)) { value_type const& v = *n; // third load // ... } ``` 217/10000 · 217
11 :22
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Iterators are displayed similarly to their standard counterparts. An iterator is displayed as though it were the element that it points to. An end iterator is simply displayed as `{ end iterator }`. 198/10000 · 198