2. Boost Unordered Translation (zh_Hans)
3. Doc / Modules / Root / Pages / Buckets (adoc)
4. Chinese (Simplified Han script)
5. Zen

50 :133
	English 2+^h| *Open-addressing and concurrent containers only* h|*Method* h|*Description*
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 2+^h| *仅限开放寻址与并发容器* h|*方法* h|*描述* 33/810 · 81 Needs editing
51 :136
	English `size_type max_load() const`
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — `size_type max_load() const` 28/280 · 28 Needs editing
52 :136
	English Returns the maximum number of allowed elements in the container before rehash.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 返回容器触发重新哈希前所允许容纳的最大元素数量。 24/780 · 78 Needs editing
53 :141
	English A note on `max_load` for open-addressing and concurrent containers: the maximum load will be (`max_load_factor() * bucket_count()`) right after `rehash` or on container creation, but may slightly decrease when erasing elements in high-load situations. For instance, if we have a `xref:reference/unordered_flat_map.adoc#unordered_flat_map[boost::unordered_flat_map]` with `size()` almost at `max_load()` level and then erase 1,000 elements, `max_load()` may decrease by around a few dozen elements. This is done internally by Boost.Unordered in order to keep its performance stable, and must be taken into account when planning for rehash-free insertions.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 关于开放寻址与并发容器的 `max_load` 注意事项：在容器创建或执行 `rehash` 后，最大负载值将保持为 `max_load_factor() * bucket_count()` ；但在高负载场景下执行元素删除操作时，该值可能轻微下降。例如，若某个 xref:reference/unordered_flat_map.adoc#unordered_flat_map[boost::unordered_flat_map] 的 `size()` 已接近 `max_load()` 阈值，随后删除 1,000 个元素时， `max_load()` 可能减少约数十个元素。此机制是Boost.Unordered为保持性能稳定而采取的内部机制，用户在规划无重组插入操作时需予以考虑。 342/6540 · 654 Needs editing
The translation has come to an end.