boostorg/unordered
1
0
Fork 1
mirror of https://github.com/boostorg/unordered.git synced 2026-05-03 19:30:53 +02:00
Code Issues Packages Projects Releases Wiki Activity

The max_load issue was fixed in the standard ages ago

Browse Source
This commit is contained in:
Daniel James
2017-10-05 10:54:22 +01:00
parent 6b5b968b97
commit 4ac8a45a34
2 changed files with 5 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/buckets.qbk
+2 -5
View File
@@ -160,12 +160,9 @@ 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:
x.rehash((x.size() + n) / x.max_load_factor() + 1);
x.rehash((x.size() + n) / x.max_load_factor());
[blurb Note: `rehash`'s argument is the minimum number of buckets, not the
number of elements, which is why the new size is divided by the maximum load factor. The
`+ 1` guarantees there is no invalidation; without it, reallocation could occur
if the number of bucket exactly divides the target size, since the container is
allowed to rehash when the load factor is equal to the maximum load factor.]
number of elements, which is why the new size is divided by the maximum load factor.]
[endsect]