public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lichray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/58403] __normal_iterator triggers odr-use
Date: Thu, 12 Sep 2013 14:59:00 -0000	[thread overview]
Message-ID: <bug-58403-4-AL2A2U1fbR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58403-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58403

--- Comment #9 from Zhihao Yuan <lichray at gmail dot com> ---
(In reply to Jonathan Wakely from comment #7)
> [...] It is unspecified whether
> "it += A::a" is an odr-use or not.

Well, it's true, but I guess the primary purpose of making
containers' iterator implementation-defined is to allow
raw pointers instead of to make it harder to use...

I think we have the consensus that this is OK to change,
though.


  parent reply	other threads:[~2013-09-12 14:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12 10:30 [Bug libstdc++/58403] New: " lichray at gmail dot com
2013-09-12 10:48 ` [Bug libstdc++/58403] " paolo.carlini at oracle dot com
2013-09-12 10:53 ` lichray at gmail dot com
2013-09-12 11:04 ` paolo.carlini at oracle dot com
2013-09-12 11:43 ` redi at gcc dot gnu.org
2013-09-12 13:00 ` lichray at gmail dot com
2013-09-12 13:44 ` paolo.carlini at oracle dot com
2013-09-12 14:31 ` redi at gcc dot gnu.org
2013-09-12 14:38 ` paolo.carlini at oracle dot com
2013-09-12 14:59 ` lichray at gmail dot com [this message]
2013-09-12 15:04 ` redi at gcc dot gnu.org
2013-09-12 15:15 ` paolo at gcc dot gnu.org
2013-09-12 15:17 ` paolo.carlini at oracle dot com

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-58403-4-AL2A2U1fbR@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).