From cppreference.com
iteratorerase(iteratorpos); (1)(since C++11)
(until C++23)iteratorerase(iteratorpos)requires(!std::same_as<iterator,const_iterator>);(since C++23)iteratorerase(const_iteratorpos); (2) (since C++11)iteratorerase(const_iteratorfirst,const_iteratorlast); (3) (since C++11)size_typeerase(constKey&key); (4) (since C++11)template<classK>size_typeerase(K&&x); (5)(since C++23)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.)
1,2) Removes the element at pos. Only one overload is provided if iterator and const_iterator are the same type.
3) Removes the elements in the range [first, last), which must be a valid range in *this.
4) Removes the element (if one exists) with the key equivalent to key.
5) Removes all elements with key that compares equivalent to the value x. This overload participates in overload resolution only if Hash::is_transparent and KeyEqual::is_transparent are valid and each denotes a type, 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 valid and dereferenceable. Thus the
iterator (which is valid, but is not dereferenceable) cannot be used as a value for pos.
Parameters
pos - iterator to the element to remove first, last - the pair of iterators defining the
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
1-3) Iterator following the last removed element.
4) Number of elements removed (0 or 1).
5) Number of elements removed.
Exceptions
1-3) Throws nothing.
4,5) Any exceptions thrown by the Hash and KeyEqual object.
Complexity
Given an instance c of unordered_set:
1,2) Average case: constant, worst case: c.size().
3) Average case: std::distance(first,last), worst case: c.size().
4) Average case: c.count(key), worst case: c.size().
5) Average case: c.count(x), worst case: c.size().
Notes
macroValueStdFeature
__cpp_lib_associative_heterogeneous_erasure
(C++23)Heterogeneous erasure in
and
unordered associative containers
; overload (
)Example
Run this code
#include<unordered_set>#include<iostream>intmain(){std::unordered_set<int>c={1,2,3,4,1,2,3,4};autoprint=[&c]{std::cout<<"c = { ";for(intn:c)std::cout<<n<<' ';std::cout<<"}\n";};print();std::cout<<"Erase all odd numbers:\n";for(autoit=c.begin();it!=c.end();){if(*it%2!=0)it=c.erase(it);else++it;}print();std::cout<<"Erase 1, erased count: "<<c.erase(1)<<'\n';std::cout<<"Erase 2, erased count: "<<c.erase(2)<<'\n';std::cout<<"Erase 2, erased count: "<<c.erase(2)<<'\n';print();}Possible output:
c = { 1 2 3 4 } Erase all odd numbers: c = { 2 4 } Erase 1, erased count: 0 Erase 2, erased count: 1 Erase 2, erased count: 0 c = { 4 } Defect reports
The following behavior-changing defect reports were applied retroactively to previously published C++ standards.
DR Applied to Behavior as published Correct behavior
C++11 there was ambiguity for overload (2)added overload (1)
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)