30 This collection implementation is efficient when the `inserts()` to the collection come
31 in blocks, then the lookups (`find()` or `operator[]()`) in blocks, then the `inserts(...)` again.
32 This is because the collection only sorts itself when it is unsorted and a lookup occurs.
33 Non-unique keys are allowed, and the groups of non-unique keys are adjacent (after sorting) then the range of the "unique" key is multiple values.
34
35 The complexity is (assuming default container of `std::vector`, which affects these complexities):
36 -# Copy: O(n), worst-case.
37
38 More notes:
39 ===========
40 -# After sorting, non-unique keys are guaranteed to be adjacent in the multimap.
41 -# The base container can be pretty much any STL container. The obvious candidates are `std::vector` or `std:list`. The choice will affect the complexities above. The advantage of `std::vector` over `std::list` is locality of reference: The data elements are guaranteed to be local to each other, unlike `std::list`. Alternatively `std:list` has better complexity than `std::vector` for some of the operations. Choose wisely.
165 This collection implementation is efficient when the `inserts()` to the collection come
166 in blocks, then the lookups (`find()` or `operator[]()`) in blocks, then the `inserts()` again.
167 This is because the collection only sorts itself when it is unsorted and a lookup occurs.
168 Non-unique keys are allowed, and the groups of non-unique keys are adjacent (after sorting) then the range of the "unique" key is multiple values.
169
170 The complexity is (assuming default container of `std::vector`, which affects these complexities):
171 -# Copy: O(n), worst-case.
172
173 More notes:
174 ===========
175 -# After sorting, non-unique keys are guaranteed to be adjacent in the multiset.
176 -# The base container can be pretty much any STL container. The obvious candidates are `std::vector` or `std:list`. The choice will affect the complexities above. The advantage of `std::vector` over `std::list` is locality of reference: The data elements are guaranteed to be local to each other, unlike `std::list`. Alternatively `std:list` has better complexity than `std::vector` for some of the operations. Choose wisely.