public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13640] Failing to reject class template partial specialization which can never be selected
Date: Mon, 01 Mar 2004 01:14:00 -0000	[thread overview]
Message-ID: <20040301011436.17237.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040110200828.13640.giovannibajo@libero.it>


------- Additional Comments From giovannibajo at libero dot it  2004-03-01 01:14 -------
(In reply to comment #8)

> And if you're going to make that a warning, please
> put it off by default, because that is going to waste cycles and increase
> compile-time -- because, you'll need to do partial template ordering.

I'm looking into a simple sintactic solution. Within 
process_partial_specialization, I go through the inner_args and check if the 
template parameters appear only in non-deduced contexts (for a start: within 
nested-name-specifiers). If that's true, I emit a warning. Am I missing 
something? It looks like it's going to work.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13640


  parent reply	other threads:[~2004-03-01  1:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10 20:08 [Bug c++/13640] New: [3.3/3.4 regression] " giovannibajo at libero dot it
2004-01-10 20:10 ` [Bug c++/13640] " giovannibajo at libero dot it
2004-01-10 20:44 ` pinskia at gcc dot gnu dot org
2004-01-10 22:24 ` steven at gcc dot gnu dot org
2004-01-10 23:25 ` gdr at integrable-solutions dot net
2004-01-10 23:26 ` gdr at integrable-solutions dot net
2004-01-10 23:34 ` pinskia at gcc dot gnu dot org
2004-01-11  0:11 ` [Bug c++/13640] " giovannibajo at libero dot it
2004-01-11  0:11 ` giovannibajo at libero dot it
2004-01-11  0:11 ` [Bug c++/13640] [3.3/3.4 regression] " giovannibajo at libero dot it
2004-01-11  0:19 ` [Bug c++/13640] " gdr at integrable-solutions dot net
2004-01-11  0:19 ` gdr at integrable-solutions dot net
2004-01-11  0:45 ` giovannibajo at libero dot it
2004-01-11  3:12 ` pinskia at gcc dot gnu dot org
2004-01-12 15:56 ` bangerth at dealii dot org
2004-01-15 19:49 ` theodore dot papadopoulo at sophia dot inria dot fr
2004-03-01  0:48 ` gdr at gcc dot gnu dot org
2004-03-01  1:14 ` giovannibajo at libero dot it [this message]
2004-03-01  1:31 ` gdr at integrable-solutions dot net
2005-06-13  3:38 ` pinskia at gcc dot gnu dot 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=20040301011436.17237.qmail@sources.redhat.com \
    --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).