public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104443] common_iterator<I, S>::operator-> is not correctly implemented
Date: Fri, 29 Jul 2022 09:12:02 +0000 [thread overview]
Message-ID: <bug-104443-4-XxcRYqQTdc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104443-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104443
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|SUSPENDED |RESOLVED
Target Milestone|--- |13.0
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jiang An from comment #3)
> LWG3672 has been adopted, so no change is needed and this issue can be
> closed. Although it might be more clear to use auto instead of
> decltype(auto).
Agreed, and done. Thanks for the report and update.
next prev parent reply other threads:[~2022-07-29 9:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 17:40 [Bug libstdc++/104443] New: " de34 at live dot cn
2022-02-08 17:48 ` [Bug libstdc++/104443] " redi at gcc dot gnu.org
2022-02-09 16:08 ` redi at gcc dot gnu.org
2022-02-09 20:49 ` redi at gcc dot gnu.org
2022-02-12 11:52 ` redi at gcc dot gnu.org
2022-07-28 10:55 ` de34 at live dot cn
2022-07-29 9:11 ` cvs-commit at gcc dot gnu.org
2022-07-29 9:12 ` redi at gcc dot gnu.org [this message]
2022-08-03 13:47 ` cvs-commit at gcc dot gnu.org
2022-08-03 13:49 ` redi at gcc dot gnu.org
2022-09-07 17:49 ` cvs-commit at gcc dot gnu.org
2022-09-07 17:53 ` 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-104443-4-XxcRYqQTdc@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).