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 c++/109663] False positive? Converting from initializer list would use explicit constructor Date: Fri, 28 Apr 2023 14:56:00 +0000 [thread overview] Message-ID: <bug-109663-4-L7t21tlHAE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109663-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109663 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpolacek at gcc dot gnu.org --- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> --- N.B. Please don't close bugs as FIXED when nothing was fixed in GCC. There are other resolutions to use when the bug report is invalid, e.g. INVALID. But in this case I'm not actually sure what the right behaviour is, maybe Marek can take a look.
next prev parent reply other threads:[~2023-04-28 14:56 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-28 9:56 [Bug c++/109663] New: " carlosgalvezp at gmail dot com 2023-04-28 9:57 ` [Bug c++/109663] " carlosgalvezp at gmail dot com 2023-04-28 11:50 ` carlosgalvezp at gmail dot com 2023-04-28 12:26 ` redi at gcc dot gnu.org 2023-04-28 14:04 ` carlosgalvezp at gmail dot com 2023-04-28 14:52 ` redi at gcc dot gnu.org 2023-04-28 14:56 ` redi at gcc dot gnu.org [this message] 2023-04-28 14:57 ` pinskia at gcc dot gnu.org 2023-04-28 14:58 ` carlosgalvezp at gmail dot com 2023-04-28 15:02 ` 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-109663-4-L7t21tlHAE@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: linkBe 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).