Issue 41 in google-sparsehash: Error in documentation of max_load_factor and min_load_factor
codesite...@google.com
Owner: ----
New issue 41 by tenox2800: Error in documentation of max_load_factor and
min_load_factor
http://code.google.com/p/google-sparsehash/issues/detail?id=41
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.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
codesite...@google.com
Status: Started
Comment #1 on issue 41 by csilvers: Error in documentation of
max_load_factor and min_load_factor
http://code.google.com/p/google-sparsehash/issues/detail?id=41
Oops! In fact, the prototype is totally wrong. I've fixed it on all 4
pages, which
will be in the next release.
codesite...@google.com
Comment #2 on issue 41 by tenox2800: Error in documentation of
http://code.google.com/p/google-sparsehash/issues/detail?id=41
Great! Thanks again!
codesite...@google.com
Labels: Type-Defect Priority-Medium
Comment #3 on issue 41 by csilvers: Error in documentation of
max_load_factor and min_load_factor
http://code.google.com/p/google-sparsehash/issues/detail?id=41
(No comment was entered for this change.)
google-s...@googlecode.com
Comment #4 on issue 41 by csilvers: Error in documentation of
http://code.google.com/p/google-sparsehash/issues/detail?id=41
This should be resolved in sparsehash 1.6, just released.
google-s...@googlecode.com
Status: Fixed
Comment #5 on issue 41 by csilvers: Error in documentation of
max_load_factor and min_load_factor
http://code.google.com/p/google-sparsehash/issues/detail?id=41
(No comment was entered for this change.)
--