public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "scottbaldwin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57239] cannot handle inner/nested class templates with non-type parameter packs that were declared in the outer/containing class
Date: Wed, 26 Jun 2013 12:08:00 -0000 [thread overview]
Message-ID: <bug-57239-4-1L7RAdHpaf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57239-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57239
--- Comment #8 from etherice <scottbaldwin at gmail dot com> ---
(In reply to Jonathan Wakely from comment #7)
> (In reply to etherice from comment #6)
> > 2) My example was complete except for needing a couple #includes [...]
>
> So it was not complete then!
>
> This bug has already been confirmed, except for updating the status (see how
> unhelpful that is?)
>
> If five people try to analyse the bug report then five people have to waste
> their time fixing your testcase because you didn't paste in two little lines
> which you already had in your version of the code.
>
> I think this can be confirmed, but please read the bug submission guidelines
> next time.
Good, and points taken.
next prev parent reply other threads:[~2013-06-26 12:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 15:53 [Bug c++/57239] New: GCC " scottbaldwin at gmail dot com
2013-05-11 13:14 ` [Bug c++/57239] " daniel.kruegler at googlemail dot com
2013-06-26 9:53 ` scottbaldwin at gmail dot com
2013-06-26 10:16 ` redi at gcc dot gnu.org
2013-06-26 10:29 ` redi at gcc dot gnu.org
2013-06-26 10:55 ` scottbaldwin at gmail dot com
2013-06-26 11:32 ` redi at gcc dot gnu.org
2013-06-26 12:08 ` scottbaldwin at gmail dot com [this message]
2013-06-26 14:23 ` scottbaldwin at gmail dot com
2013-06-26 15:23 ` redi at gcc dot gnu.org
2013-06-26 16:04 ` scottbaldwin at gmail dot com
2013-06-26 17:56 ` paolo.carlini at oracle dot com
2021-12-03 3:45 ` 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-57239-4-1L7RAdHpaf@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).