public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jlame646 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/113300] New: GCC rejects valid program involving explicit and non explicit default constructors Date: Wed, 10 Jan 2024 02:53:30 +0000 [thread overview] Message-ID: <bug-113300-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113300 Bug ID: 113300 Summary: GCC rejects valid program involving explicit and non explicit default constructors Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jlame646 at gmail dot com Target Milestone: --- The following valid program is rejected by gcc and clang but accepted by msvc. https://godbolt.org/z/Y3x8nP11M ``` struct A { explicit A(int = 10); A()= default; }; A a = {}; //msvc ok but gcc and clang fails here ``` GCC says: ``` <source>:8:8: error: conversion from '<brace-enclosed initializer list>' to 'A' is ambiguous 8 | A a = {}; //msvc ok but gcc and clang fails here | ^ <source>:5:3: note: candidate: 'constexpr A::A()' 5 | A()= default; | ^ <source>:4:12: note: candidate: 'A::A(int)' 4 | explicit A(int = 10); ``` The reason why this is valid is discussed here: https://stackoverflow.com/questions/77788861/ambiguous-constructor-error-in-gcc-but-not-in-msvc
next reply other threads:[~2024-01-10 2:53 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-10 2:53 jlame646 at gmail dot com [this message] 2024-01-10 2:55 ` [Bug c++/113300] " pinskia at gcc dot gnu.org 2024-01-10 2:56 ` pinskia at gcc dot gnu.org 2024-01-10 2:59 ` [Bug c++/113300] GCC rejects valid program involving copy list initialization A a = {} of a class with " jlame646 at gmail dot com 2024-01-10 3:03 ` jlame646 at gmail dot com 2024-01-10 18:59 ` mpolacek at gcc dot gnu.org 2024-01-30 16:15 ` mpolacek at gcc dot gnu.org 2024-04-23 22:34 ` mpolacek 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-113300-4@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).