public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94819] [10 Regression] Inherited and constrained constructors are "ambiguous" even if they aren't Pt. 2 Date: Tue, 28 Apr 2020 17:04:51 +0000 [thread overview] Message-ID: <bug-94819-4-sLEMr8d6L0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94819-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94819 Daniel Krügler <daniel.kruegler at googlemail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.kruegler@googlemail. | |com --- Comment #2 from Daniel Krügler <daniel.kruegler at googlemail dot com> --- After removal of any library dependencies: ```c++ template<class, class> inline constexpr bool is_same_v = false; template<class T> inline constexpr bool is_same_v<T, T> = true; template <typename component_types> struct alphabet_tuple_base { template <typename component_type> requires is_same_v<component_type, component_types> constexpr alphabet_tuple_base(component_type) {} // commenting out constexpr works?! template <typename indirect_component_type> requires (!is_same_v<indirect_component_type, component_types>) alphabet_tuple_base(indirect_component_type) {} }; template <typename sequence_alphabet_t> struct structured_rna : alphabet_tuple_base<sequence_alphabet_t> { using base_type = alphabet_tuple_base<sequence_alphabet_t>; using base_type::base_type; }; struct dna4 {}; struct rna4 {}; structured_rna<rna4> t1{rna4{}}; // commenting out any of these works?! structured_rna<rna4> t2{dna4{}}; // commenting out any of these works?! structured_rna<rna4> t3{rna4{}}; // commenting out any of these works?! int main() {} ```
next prev parent reply other threads:[~2020-04-28 17:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-28 13:02 [Bug c++/94819] New: " gcc-bugs at marehr dot dialup.fu-berlin.de 2020-04-28 13:21 ` [Bug c++/94819] " gcc-bugs at marehr dot dialup.fu-berlin.de 2020-04-28 13:37 ` rguenth at gcc dot gnu.org 2020-04-28 17:04 ` daniel.kruegler at googlemail dot com [this message] 2020-04-28 17:37 ` ppalka at gcc dot gnu.org 2020-04-29 2:09 ` cvs-commit at gcc dot gnu.org 2020-04-29 2:11 ` ppalka 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-94819-4-sLEMr8d6L0@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).