forked from boostorg/unordered
Fill in more of the unordered container documentation.
[SVN r3042]
This commit is contained in:
@@ -20,9 +20,8 @@ on average. The worst case complexity is linear, but that occurs rarely and
|
||||
with some care, can be avoided.
|
||||
|
||||
Also, the existing containers require a 'less than' comparison object
|
||||
to order their elements. For some data types this is impracticle.
|
||||
It might be slow to calculate, or even impossible. On the other hand, in a hash
|
||||
table, then elements aren't ordered - but you need an equality function
|
||||
to order their elements. For some data types this is impossible to implement
|
||||
or isn't practicle. For a hash table you need an equality function
|
||||
and a hash function for the key.
|
||||
|
||||
So the __tr1__ introduced the unordered associative containers, which are
|
||||
|
||||
Reference in New Issue
Block a user