public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113884] GCC rejects valid program saying ambiguous call when using std::vector
Date: Mon, 12 Feb 2024 05:01:30 +0000 [thread overview]
Message-ID: <bug-113884-4-HSZV2RFVTy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113884-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113884
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> Reduced to:
> ```
> struct B
> {
> B(double);
> };
>
> struct C
> {
> C(int);
> };
>
>
> void func(B);
> void func(C);
>
> int main() {
> func({ 4.2 });
> }
> ```
Actually C constructor should be:
explicit C(int);
next prev parent reply other threads:[~2024-02-12 5:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 4:51 [Bug c++/113884] New: " jlame646 at gmail dot com
2024-02-12 4:58 ` [Bug c++/113884] " pinskia at gcc dot gnu.org
2024-02-12 5:01 ` pinskia at gcc dot gnu.org [this message]
2024-02-12 5:03 ` pinskia at gcc dot gnu.org
2024-02-12 5:18 ` jlame646 at gmail dot com
2024-02-12 5:22 ` pinskia at gcc dot gnu.org
2024-02-12 5:25 ` pinskia at gcc dot gnu.org
2024-02-12 5:47 ` jlame646 at gmail dot com
2024-02-12 5:59 ` pinskia at gcc dot gnu.org
2024-02-12 7:58 ` jlame646 at gmail 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-113884-4-HSZV2RFVTy@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).