public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle 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 17:56:00 -0000 [thread overview] Message-ID: <bug-57239-4-aXAi7E0M9a@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 #13 from Paolo Carlini <paolo.carlini at oracle dot com> --- Curious, I understand, assuming they don't take new as a solid indication that a fix is forthcoming. assigned normally is more reliable for that, still not much more, unless, as I tried to explain, there are other reasons like the bug is a regression, a release is close, etc.
next prev parent reply other threads:[~2013-06-26 17:56 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 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 [this message] 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-aXAi7E0M9a@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: 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).