std::unordered_multimap<Key,T,Hash,KeyEqual,Allocator>:: erase
|
iterator erase
(
iterator pos
)
;
|
(1) |
(since C++11)
(constexpr since C++26) |
|
iterator erase
(
const_iterator pos
)
;
|
(2) |
(since C++11)
(constexpr since C++26) |
|
iterator erase
(
const_iterator first, const_iterator last
)
;
|
(3) |
(since C++11)
(constexpr since C++26) |
|
size_type erase
(
const
Key
&
key
)
;
|
(4) |
(since C++11)
(constexpr since C++26) |
|
template
<
class
K
>
size_type erase ( K && x ) ; |
(5) |
(since C++23)
(constexpr since C++26) |
Removes specified elements from the container.The order of the remaining elements is preserved. (This makes it possible to erase individual elements while iterating through the container.)
[
first
,
last
)
, which must be a valid range in
*
this
.
Hash
and
KeyEqual
are both
transparent
, and neither
iterator
nor
const_iterator
is implicitly convertible from
K
. This assumes that such
Hash
is callable with both
K
and
Key
type, and that the
KeyEqual
is transparent, which, together, allows calling this function without constructing an instance of
Key
.
References and iterators to the erased elements are invalidated. Other iterators and references are not invalidated.
The iterator pos must be dereferenceable. Thus the end() iterator (which is valid, but is not dereferenceable) cannot be used as a value for pos .
Contents |
Parameters
| pos | - | iterator to the element to remove |
| first, last | - | the pair of iterators defining the range of elements to remove |
| key | - | key value of the elements to remove |
| x | - | a value of any type that can be transparently compared with a key denoting the elements to remove |
Return value
Exceptions
Hash
and
KeyEqual
object.
Complexity
Given an instance
c
of
unordered_multimap
:
Notes
| Feature-test macro | Value | Std | Feature |
|---|---|---|---|
__cpp_lib_associative_heterogeneous_erasure
|
202110L
|
(C++23) | Heterogeneous erasure in associative containers and unordered associative containers ; overload ( 5 ) |
Example
#include <unordered_map> #include <iostream> int main() { std::unordered_multimap<int, std::string> c = { {1, "one"}, {2, "two"}, {3, "three"}, {4, "four"}, {5, "five"}, {6, "six"} }; // erase all odd numbers from c for (auto it = c.begin(); it != c.end();) { if (it->first % 2 != 0) it = c.erase(it); else ++it; } for (auto& p : c) std::cout << p.second << ' '; std::cout << '\n'; }
Possible output:
two four six
Defect reports
The following behavior-changing defect reports were applied retroactively to previously published C++ standards.
| DR | Applied to | Behavior as published | Correct behavior |
|---|---|---|---|
| LWG 2059 | C++11 | there was ambiguity for overload ( 2 ) | added overload ( 1 ) |
| LWG 2356 | C++11 |
the order of non-equivalent elements that are
not erased was not guaranteed to be preserved |
required to be preserved |
See also
|
clears the contents
(public member function) |