public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lichray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56480] Explicit specialization in a namespace enclosing the specialized template
Date: Fri, 29 Nov 2013 23:49:00 -0000 [thread overview]
Message-ID: <bug-56480-4-fqia12dr6i@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56480-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56480
Zhihao Yuan <lichray at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lichray at gmail dot com
--- Comment #3 from Zhihao Yuan <lichray at gmail dot com> ---
(In reply to Nathan Ridge from comment #2)
> (In reply to comment #1)
> > I think this is
> > http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#374
>
> Ah, I see. The code is accepted if a declaration (without definition) of the
> specialization is placed in the namespace. Didn't realize that.
?? That was the c++03 status, and the new wording ("or to a specialization
thereof") relaxed this requirement.
Has this been implemented?
next prev parent reply other threads:[~2013-11-29 23:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 8:18 [Bug c++/56480] New: " zeratul976 at hotmail dot com
2013-03-05 1:29 ` [Bug c++/56480] " redi at gcc dot gnu.org
2013-03-05 4:30 ` zeratul976 at hotmail dot com
2013-11-29 23:49 ` lichray at gmail dot com [this message]
2014-11-01 15:51 ` trippels at gcc dot gnu.org
2014-11-01 18:05 ` trippels at gcc dot gnu.org
2014-11-02 11:48 ` trippels at gcc dot gnu.org
2015-04-22 12:06 ` jakub at gcc dot gnu.org
2015-07-16 9:13 ` rguenth at gcc dot gnu.org
2021-08-04 20:42 ` pinskia at gcc dot gnu.org
2021-08-23 8:33 ` pinskia 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-56480-4-fqia12dr6i@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).