https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41628
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41628
--- Comment #4 from Jonathan Wakely ---
Roland, could you please clarify the request, or I'll close this report as
WORKSFORME. What do you mean by "unstable iterator" and what is the problem you
want to solve?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41628
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
--- Comment #2 from redi at gcc dot gnu dot org 2009-10-08 09:43 ---
(In reply to comment #1)
> std::set::iterator i = s.insert(5);
Oops, that should be
std::set::iterator i = s.insert(5).first;
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41628
--- Comment #1 from redi at gcc dot gnu dot org 2009-10-08 09:42 ---
set::insert never invalidates iterators, so that's not a good example.
set::erase invalidates iterators pointing to erased elements, but debug mode
already catches that.
One problem I see with this request is that when
--
paolo dot carlini at oracle dot com changed:
What|Removed |Added
Severity|normal |enhancement
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41628
