public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66832] [concepts] parameters in requires clauses conflicting with function arguments Date: Fri, 10 Jul 2015 22:46:00 -0000 [thread overview] Message-ID: <bug-66832-4-cbC61W8yGD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66832-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66832 --- Comment #1 from Jason Merrill <jason at gcc dot gnu.org> --- Author: jason Date: Fri Jul 10 22:45:41 2015 New Revision: 225704 URL: https://gcc.gnu.org/viewcvs?rev=225704&root=gcc&view=rev Log: PR c++/66758 PR c++/66832 * gcc/cp/parser.c (cp_parser_requires_expression): Call grokparms here. (cp_parser_requirement_parameter_list): Not here. Added: branches/c++-concepts/gcc/testsuite/g++.dg/concepts/req15.C Modified: branches/c++-concepts/ChangeLog.concepts branches/c++-concepts/gcc/cp/parser.c
next prev parent reply other threads:[~2015-07-10 22:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-10 17:42 [Bug c++/66832] New: " eric.niebler at gmail dot com 2015-07-10 22:46 ` jason at gcc dot gnu.org [this message] 2015-07-10 22:52 ` [Bug c++/66832] " jason 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-66832-4-cbC61W8yGD@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).