2. Boost Unordered Translation (zh_Hans)
3. Doc / Modules / Root / Pages / Intro (adoc)
4. English
5. Zen

1 :2
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — = Introduction 14/10000 · 14
2 :4
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — :idprefix: intro_ :cpp: C++ 27/10000 · 27
3 :7
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — link:https://en.wikipedia.org/wiki/Hash_table[Hash tables^] are extremely popular computer data structures and can be found under one form or another in virtually any programming language. Whereas other associative structures such as rb-trees (used in {cpp} by `std::set` and `std::map`) have logarithmic-time complexity for insertion and lookup, hash tables, if configured properly, perform these operations in constant time on average, and are generally much faster. 468/10000 · 468
4 :13
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — {cpp} introduced __unordered associative containers__ `std::unordered_set`, `std::unordered_map`, `std::unordered_multiset` and `std::unordered_multimap` in {cpp}11, but research on hash tables hasn't stopped since: advances in CPU architectures such as more powerful caches, link:https://en.wikipedia.org/wiki/Single_instruction,_multiple_data[SIMD] operations and increasingly available link:https://en.wikipedia.org/wiki/Multi-core_processor[multicore processors] open up possibilities for improved hash-based data structures and new use cases that are simply beyond reach of unordered associative containers as specified in 2011. 633/10000 · 633
5 :21
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Boost.Unordered offers a catalog of hash containers with different standards compliance levels, performances and intented usage scenarios: 138/10000 · 138
6 :27
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — ^h| ^h|*Node-based* ^h|*Flat* 29/10000 · 29
7 :31
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — ^.^h|*Closed addressing* ^m| boost::unordered_set + boost::unordered_map + boost::unordered_multiset + boost::unordered_multimap ^| 131/10000 · 131
8 :39
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — ^.^h|*Open addressing* ^m| boost::unordered_node_set + boost::unordered_node_map ^m| boost::unordered_flat_set + boost::unordered_flat_map 138/10000 · 138
9 :45
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — ^.^h|*Concurrent* ^| `boost::concurrent_node_set` + `boost::concurrent_node_map` ^| `boost::concurrent_flat_set` + `boost::concurrent_flat_map` 143/10000 · 143
10 :53
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — **Closed-addressing containers** are fully compliant with the C++ specification 79/10000 · 79
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
12 :56
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — **Open-addressing containers** rely on much faster data structures and algorithms 81/10000 · 81
13 :57
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — (more than 2 times faster in typical scenarios) while slightly diverging from the standard interface to accommodate the implementation. There are two variants: **flat** (the fastest) and **node-based**, which provide pointer stability under rehashing at the expense of being slower. 282/10000 · 282
14 :61
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Finally, **concurrent containers** are designed and implemented to be used in high-performance 94/10000 · 94
15 :62
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — multithreaded scenarios. Their interface is radically different from that of regular C++ containers. Flat and node-based variants are provided. 143/10000 · 143
16 :65
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — All sets and maps in Boost.Unordered are instantiatied similarly as `std::unordered_set` and `std::unordered_map`, respectively: 128/10000 · 128
17 :91
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Storing an object in an unordered associative container requires both a key equality function and a hash function. The default function objects in the standard containers support a few basic types including integer types, floating point types, pointer types, and the standard strings. Since Boost.Unordered uses link:../../../../container_hash/index.html[boost::hash^] it also supports some other types, including standard containers. To use any types not supported by these methods you have to extend Boost.Hash to support the type or use your own custom equality predicates and hash functions. See the xref:hash_equality.adoc#hash_equality[Equality Predicates and Hash Functions], section for more details. 708/10000 · 708
The translation has come to an end.