public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98942] [C++23] Implement P1102R2 - Down with ()!
Date: Fri, 26 Feb 2021 10:09:28 +0000 [thread overview]
Message-ID: <bug-98942-4-EKBjNPojuH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98942-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98942
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
https://gcc.gnu.org/g:0f161cc8494cf7283a16fa9ebbcf8fd121bab68d
commit r11-7419-g0f161cc8494cf7283a16fa9ebbcf8fd121bab68d
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Feb 26 10:44:52 2021 +0100
c++: Implement P1102R2 - Down with ()!
The following patch implements P1102R2.
For attributes, we have already attribute parsing before the parameter
declarations and so when that is omitted, if the attributes are first we
already accept it.
2021-02-26 Jakub Jelinek <jakub@redhat.com>
* parser.c (cp_parser_lambda_declarator_opt): Implement
P1102R2 - Down with ()! Make ()s optional before lambda specifiers
for -std={c,gnu}++2b or with pedwarn in earlier versions.
* g++.dg/cpp23/lambda-specifiers1.C: New test.
Feature test macro not added yet.
https://github.com/cplusplus/draft/pull/4513 doesn't mention anything.
next prev parent reply other threads:[~2021-02-26 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 20:00 [Bug c++/98942] New: " mpolacek at gcc dot gnu.org
2021-02-02 20:00 ` [Bug c++/98942] " mpolacek at gcc dot gnu.org
2021-02-25 18:49 ` mpolacek at gcc dot gnu.org
2021-02-26 10:09 ` jakub at gcc dot gnu.org [this message]
2021-03-25 15:58 ` mpolacek 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-98942-4-EKBjNPojuH@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).