public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: giovannibajo@libero.it To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, notbob@tessellation.com Subject: Re: c++/10646: [3.3/3.4 regression] non-const reference is incorrectly matched in a "const T" partial specialization Date: Wed, 07 May 2003 00:17:00 -0000 [thread overview] Message-ID: <20030507001750.9467.qmail@sources.redhat.com> (raw) Old Synopsis: is_const<T> treats references and functions as const New Synopsis: [3.3/3.4 regression] non-const reference is incorrectly matched in a "const T" partial specialization State-Changed-From-To: open->analyzed State-Changed-By: bajo State-Changed-When: Wed May 7 00:17:50 2003 State-Changed-Why: The bug for function types is confirmed in 3.2 but it's fixed in 3.3 (20030503) and 3.4 (20030503). It might be fixed in 3.2.3 as well, I don't have that version. There still is a bug with references, though: --------------------------------- template <typename T> struct is_const { typedef int type; }; template <typename T> struct is_const<const T> {}; is_const<bool&>::type a; --------------------------------- This should compile (but I'm not 100% sure because this very part of the standard is still a bit misterious for me), and it does on MSVC71 and Comeau/EDG, but fails with GCC 3.3 and 3.4. Since it worked in 2.95, I rate this as a regression. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10646
next reply other threads:[~2003-05-07 0:17 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-07 0:17 giovannibajo [this message] 2003-05-07 0:26 Giovanni Bajo
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=20030507001750.9467.qmail@sources.redhat.com \ --to=giovannibajo@libero.it \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=notbob@tessellation.com \ /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).