public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94568] template specialization of equivalent nontype template argument involving member pointer considered distinct
Date: Wed, 15 Apr 2020 15:49:43 +0000	[thread overview]
Message-ID: <bug-94568-4-NPaFOIi2GE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94568-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94568

--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Another test case, this one not involving pointers.  Somehow the form of the
initializer (= 0 vs { }) makes a difference.

$ cat t.C && gcc -O2 -c -Wall -std=c++2a t.C
template <C> struct D { };

constexpr const int i0 = 0;
constexpr const int i_{ };

static_assert (i0 == i_);

typedef D<C{ { 0, 1 } }>   DC01;
typedef D<C{ { i0, 1 } }>  DC01;
typedef D<C{ { i_, 1 } }>  DC01;
t.C:11:28: error: conflicting declaration ‘typedef struct D<C{int [2]{0, 1}}>
DC01’
   11 | typedef D<C{ { i_, 1 } }>  DC01;
      |                            ^~~~
t.C:10:28: note: previous declaration as ‘typedef struct D<C{int [2]{0, 1}}>
DC01’
   10 | typedef D<C{ { i0, 1 } }>  DC01;
      |                            ^~~~

  reply	other threads:[~2020-04-15 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-12 20:19 [Bug c++/94568] New: " msebor at gcc dot gnu.org
2020-04-15 15:49 ` msebor at gcc dot gnu.org [this message]
2020-04-15 16:51 ` [Bug c++/94568] " ensadc at mailnesia dot com
2020-11-16 22:17 ` 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-94568-4-NPaFOIi2GE@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).