This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of C++20 status.
unordered_meow::merge()
has incorrect Throws: clauseSection: 23.2.8 [unord.req] Status: C++20 Submitter: Tim Song Opened: 2017-06-14 Last modified: 2021-02-25
Priority: 0
View other active issues in [unord.req].
View all other issues in [unord.req].
View all issues with C++20 status.
Discussion:
As pointed out in this StackOverflow question,
unordered_{map,multimap,set,multiset}::merge()
may need to rehash to maintain its
max_load_factor
invariant, which may require allocation, which may throw.
[2017-07 Toronto Monday issue prioritization]
Priority 0; move to Ready
Proposed resolution:
This wording is relative to N4659.
In 23.2.8 [unord.req], edit Table 91 "Unordered associative container requirements" as indicated:
Table 91 — Unordered associative container requirements (in addition to container) Expression Return type Assertion/note
pre-/post-conditionComplexity …
a.merge(a2)
void
Requires: a.get_allocator() == a2.get_allocator()
.
Attempts to extract each element ina2
and insert it intoa
using the hash function and key equality predicate ofa
. In containers with unique keys, if there is an element ina
with key equivalent to the key of an element froma2
, then that element is not extracted froma2
.
Postconditions: Pointers and references to the transferred elements ofa2
refer to those same elements but as members ofa
. Iterators referring to the transferred elements and all iterators referring toa
will be invalidated, but iterators to elements remaining ina2
will remain valid.
Throws: Nothing unless the hash function or key equality predicate throws.Average case 𝒪(N), where N is a2.size()
.
Worst case 𝒪(N*a.size()+
N).…