Error in documentation of max_load_factor and min_load_factor

[GoogleCodeExporter]

The documentation for sparse_hash_map reads: 
float max_load_factor(size_t new_grow)
and 
float min_load_factor(size_t new_grow)

In both of these cases it seems that new_grow is a float not a size_t. 

Original issue reported on code.google.com by tenox2...@gmail.com on 14 May 2009 at 7:05

[GoogleCodeExporter]

Oops!  In fact, the prototype is totally wrong.  I've fixed it on all 4 pages, 
which
will be in the next release.

Original comment by csilv...@gmail.com on 15 May 2009 at 3:46

• Changed state: Started

[GoogleCodeExporter]

Great! Thanks again!

Original comment by tenox2...@gmail.com on 15 May 2009 at 5:50

[GoogleCodeExporter]

Original comment by csilv...@gmail.com on 12 Jun 2009 at 4:01

• Added labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

This should be resolved in sparsehash 1.6, just released.

Original comment by csilv...@gmail.com on 11 Jan 2010 at 10:52

[GoogleCodeExporter]

Original comment by csilv...@gmail.com on 11 Jan 2010 at 10:52

• Changed state: Fixed