http://d.puremagic.com/issues/show_bug.cgi?id=4179
--- Comment #9 from bearophile_h...@eml.cc 2013-07-20 04:05:58 PDT ---
(In reply to comment #8)
There are more possible ways to make it safe than this.
One way is to have a list of current iterations associated with each AA. Any
time an
http://d.puremagic.com/issues/show_bug.cgi?id=4179
Vladimir thecybersha...@gmail.com changed:
What|Removed |Added
CC|
http://d.puremagic.com/issues/show_bug.cgi?id=4179
--- Comment #5 from Vladimir thecybersha...@gmail.com 2011-03-29 08:29:34 PDT
---
Eh? Is getting a segfault because the data structure has been modified
considered safe?
The workaround you suggested doesn't work when removing happens several
http://d.puremagic.com/issues/show_bug.cgi?id=4179
Jonathan M Davis jmdavisp...@gmx.com changed:
What|Removed |Added
CC|
http://d.puremagic.com/issues/show_bug.cgi?id=4179
--- Comment #6 from Jonathan M Davis jmdavisp...@gmx.com 2011-03-29 08:39:23
PDT ---
segfault? I didn't think that anyone was getting a segfault from this. If
there's a segfault, then that's obviously bad. I'm not sure that it's
technically
http://d.puremagic.com/issues/show_bug.cgi?id=4179
Steven Schveighoffer schvei...@yahoo.com changed:
What|Removed |Added
CC|
http://d.puremagic.com/issues/show_bug.cgi?id=4179
--- Comment #8 from Vladimir thecybersha...@gmail.com 2011-03-29 09:58:07 PDT
---
There are more possible ways to make it safe than this.
One way is to have a list of current iterations associated with each AA. Any
time an item is removed,
http://d.puremagic.com/issues/show_bug.cgi?id=4179
--- Comment #2 from bearophile_h...@eml.cc 2010-05-26 09:49:51 PDT ---
To implement this idea the foreach() has to change a little, in nonrelease mode
it has to set and later reset a boolean flag inside the container being
iterated. So this
http://d.puremagic.com/issues/show_bug.cgi?id=4179
bearophile_h...@eml.cc changed:
What|Removed |Added
Severity|normal |enhancement
--- Comment #1
