public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc-bugzilla at contacts dot eelis dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35784]  New: Bogus inaccessibility error on variadic partial template specialization.
Date: Tue, 01 Apr 2008 01:50:00 -0000	[thread overview]
Message-ID: <bug-35784-5473@http.gcc.gnu.org/bugzilla/> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]

Consider:

  template <typename...> struct p;

  template <typename, typename> struct d;

  template <typename... A, typename... B>
  struct d<p<A...>, p<B...> > { typedef int t; };

  typedef d<p<>, p<int, float> >::t q;
  typedef d<q, d<p<int>, p<float> >::t> r; // *

  typedef d<d<p<>, p<int, float> >::t, d<p<>, p<> >::t> s;
    // error: ‘typedef int d<p<int>, p<float> >::t’ is inaccessible within
this context

The error makes no sense. In fact, it disappears if the unrelated line marked
with an asterisk is removed.


-- 
           Summary: Bogus inaccessibility error on variadic partial template
                    specialization.
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: gcc-bugzilla at contacts dot eelis dot net


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


             reply	other threads:[~2008-04-01  1:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01  1:50 gcc-bugzilla at contacts dot eelis dot net [this message]
2008-12-29  3:42 ` [Bug c++/35784] [C++0x] " pinskia at gcc dot gnu dot org
2009-01-07  0:06 ` jason at gcc dot gnu dot org
2009-01-07 20:43 ` jason at gcc dot gnu dot org
2009-01-07 20:57 ` jason 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=bug-35784-5473@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).