Why for(auto x:st)st.erase(st.find(x)); and for( it=st.begin();it!=st.end();it++)st.erase(it); causes runtime error??
# | User | Rating |
---|---|---|
1 | tourist | 3985 |
2 | jiangly | 3814 |
3 | jqdai0815 | 3682 |
4 | Benq | 3529 |
5 | orzdevinwang | 3526 |
6 | ksun48 | 3517 |
7 | Radewoosh | 3410 |
8 | hos.lyric | 3399 |
9 | ecnerwala | 3392 |
9 | Um_nik | 3392 |
# | User | Contrib. |
---|---|---|
1 | cry | 169 |
2 | maomao90 | 162 |
2 | Um_nik | 162 |
4 | atcoder_official | 161 |
5 | djm03178 | 158 |
6 | -is-this-fft- | 157 |
7 | adamant | 155 |
8 | awoo | 154 |
8 | Dominater069 | 154 |
10 | luogu_official | 150 |
Why for(auto x:st)st.erase(st.find(x)); and for( it=st.begin();it!=st.end();it++)st.erase(it); causes runtime error??
Name |
---|
Auto comment: topic has been updated by RED_in_Three_Months (previous revision, new revision, compare).
Don't know about the first example. But for the second one, once you delete using the iterator
it
, the element gets deleted as well as all iterators pointing to that element. Thusit
gets invalidated.There's an easy workaround.
set.erase(it)
returns an iterator pointing to the element next to*it
. So, you could just doit = set.erase(it)
.This issue has been nicely discussed here: https://mirror.codeforces.com/blog/entry/55393