feedc0de/boost_container_hash
1
0
Fork 0
forked from boostorg/container_hash
Code Pull Requests Activity

Update documentation

Browse Source
This commit is contained in:
Peter Dimov
2022-09-20 21:20:31 +03:00
parent e92eae9eb2
commit 85f9f8a97a
2 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/hash/notes.adoc
View File

@@ -196,8 +196,9 @@ lot of performance on the table, because processing each `char` individually
is much less efficient than processing several in bulk. is much less efficient than processing several in bulk.
In Boost 1.81, `hash_range` was changed to process elements of type `char`, In Boost 1.81, `hash_range` was changed to process elements of type `char`,
`signed char`, or `unsigned char`, four of a time. A `uint32_t` is composed `signed char`, `unsigned char`, `std::byte`, or `char8_t`, four of a time.
from `first[0]` to `first[3]`, and that `uint32_t` is fed to `hash_combine`. A `uint32_t` is composed from `first[0]` to `first[3]`, and that `uint32_t`
is fed to `hash_combine`.
In principle, when `size_t` is 64 bit, we could have used `uint64_t` instead. In principle, when `size_t` is 64 bit, we could have used `uint64_t` instead.
We do not, because this allows producing an arbitrary hash value by choosing We do not, because this allows producing an arbitrary hash value by choosing

2
doc/hash/reference.adoc
View File

@@ -225,7 +225,7 @@ Effects: ::
+ +
-- --
When `typename std::iterator_traits<It>::value_type` is not `char`, `signed char`, When `typename std::iterator_traits<It>::value_type` is not `char`, `signed char`,
`unsigned char`, `unsigned char`, `std::byte`, or `char8_t`,
[source] [source]
---- ----