public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Paolo Carlini <paolo.carlini@oracle.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ Patch] PR 69095
Date: Mon, 23 May 2016 13:32:00 -0000	[thread overview]
Message-ID: <cf8a00f8-4574-6a4e-0fd8-c3c05ff3b52b@redhat.com> (raw)
In-Reply-To: <5741F9D9.6040906@oracle.com>

On 05/22/2016 02:26 PM, Paolo Carlini wrote:
> finally sending a patch for this issue. As noticed by submitter himself,
> it appears to boil down to a rather straightforward case of not
> rejecting unexpanded parameter packs in default arguments. In order to
> handle all the combinations (in/out of class, template
> parameter/function parameter) I added calls of
> check_for_bare_parameter_packs both to cp_parser_default_argument and
> cp_parser_late_parsing_default_args

Hmm, would it make sense to check in cp_parser_initializer?

Jason

  reply	other threads:[~2016-05-23 13:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-22 18:26 Paolo Carlini
2016-05-23 13:32 ` Jason Merrill [this message]
2016-05-23 15:25   ` Paolo Carlini
2016-05-23 17:30     ` Jason Merrill

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=cf8a00f8-4574-6a4e-0fd8-c3c05ff3b52b@redhat.com \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=paolo.carlini@oracle.com \
    /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).