public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "temporal at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/58153] unordered_multimap::erase(iterator) is not constant-time when many entries have the same key
Date: Sat, 24 Aug 2013 19:16:00 -0000 [thread overview]
Message-ID: <bug-58153-4-ob3EEkbUPn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58153-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58153
--- Comment #4 from Kenton Varda <temporal at gmail dot com> ---
> This report entry made me wonder why iterators could not just be
> pointing to the node just before the one containing the pointed to value.
That's a neat idea.
I think there is an obscure issue, though. If I have an iterator pointing at
item N, and then I (separately) erase item N - 1, what happens to my iterator?
But you bring up another, simpler point: why not just have an erase_after()
method like forward_list does? That would suit my use case (although at this
point I've rewritten it to do something different).
next prev parent reply other threads:[~2013-08-24 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 10:11 [Bug libstdc++/58153] New: " temporal at gmail dot com
2013-08-14 10:35 ` [Bug libstdc++/58153] " redi at gcc dot gnu.org
2013-08-14 11:16 ` temporal at gmail dot com
2013-08-24 16:30 ` fdumont at gcc dot gnu.org
2013-08-24 19:16 ` temporal at gmail dot com [this message]
2013-08-26 20:06 ` fdumont at gcc dot gnu.org
2013-08-27 3:10 ` temporal at gmail dot com
2015-04-09 14:49 ` redi at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-58153-4-ob3EEkbUPn@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).