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??
№ | Пользователь | Рейтинг |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3823 |
3 | Benq | 3738 |
4 | Radewoosh | 3633 |
5 | jqdai0815 | 3620 |
6 | orzdevinwang | 3529 |
7 | ecnerwala | 3446 |
8 | Um_nik | 3396 |
9 | ksun48 | 3390 |
10 | gamegame | 3386 |
Страны | Города | Организации | Всё → |
№ | Пользователь | Вклад |
---|---|---|
1 | cry | 167 |
2 | Um_nik | 163 |
3 | maomao90 | 162 |
3 | atcoder_official | 162 |
5 | adamant | 159 |
6 | -is-this-fft- | 158 |
7 | awoo | 157 |
8 | TheScrasse | 154 |
9 | Dominater069 | 153 |
9 | nor | 153 |
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??
Название |
---|
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://codeforces.net/blog/entry/55393