From a07c59a64e04dee62f206dba78054312b422dfd6 Mon Sep 17 00:00:00 2001 From: Daniel James Date: Thu, 6 Dec 2007 11:41:04 +0000 Subject: [PATCH] Remove a few commented out paragraphs of mostly incorrect documentation. [SVN r41780] --- doc/buckets.qbk | 21 --------------------- 1 file changed, 21 deletions(-) diff --git a/doc/buckets.qbk b/doc/buckets.qbk index a97ff93c..24778aaa 100644 --- a/doc/buckets.qbk +++ b/doc/buckets.qbk @@ -124,25 +124,4 @@ factor is equal to the maximum load factor.] ] -[/ I'm not at all happy with this section. So I've commented it out.] - -[/ h2 Rehash Techniques] - -[/If the container has a load factor much smaller than the maximum, `rehash` -might decrease the number of buckets, reducing the memory usage. This isn't -guaranteed by the standard but this implementation will do it. - -If you want to stop the table from ever rehashing due to an insert, you can -set the maximum load factor to infinity (or perhaps a load factor that it'll -never reach - say `x.max_size()`. As you can only give a 'hint' for the maximum -load factor, this isn't guaranteed to work. But again, it'll work in this -implementation. (TODO: If an unordered container with infinite load factor -is copied, bad things could happen. So maybe this advice should be removed. Or -maybe the implementation should cope with that). - -If you do this and want to make the container rehash, `rehash` will still work. -But be careful that you only ever call it with a sufficient number of buckets -- otherwise it's very likely that the container will decrease the bucket -count to an overly small amount.] - [endsect]