From: Jakub Jelinek <jakub@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: Patrick Palka <ppalka@redhat.com>,
Jonathan Wakely <jwakely@redhat.com>,
gcc-patches@gcc.gnu.org
Subject: [PATCH] c++, v2: Allow attributes on concepts - DR 2428
Date: Tue, 15 Nov 2022 09:54:00 +0100 [thread overview]
Message-ID: <Y3NTqLfSD5kwo1SD@tucnak> (raw)
In-Reply-To: <f64ca961-5c27-e976-04ad-be5a1cd0bf1e@redhat.com>
On Mon, Nov 14, 2022 at 07:00:54PM -0500, Jason Merrill wrote:
> > The following patch adds parsing of attributes to concept definition,
> > allows deprecated attribute to be specified (some ugliness needed
> > because CONCEPT_DECL is a cp/*.def attribute and so can't be mentioned
> > in c-family/ directly; used what is used for objc method decls,
> > an alternative would be a langhook)
>
> Several of the codes in c-common.def are C++-only, you might just move it
> over?
>
> > and checks TREE_DEPRECATED in
> > build_standard_check (not sure if that is the right spot, or whether
> > it shouldn't be checked also for variable and function concepts and
> > how to write testcase coverage for that).
>
> I wouldn't bother with var/fn concepts, they're obsolete.
Ok, so like this?
The previous version passed bootstrap/regtest on x86_64-linux and i686-linux,
I'll of course test this one as well.
Jakub
next prev parent reply other threads:[~2022-11-15 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 10:40 [PATCH] c++: " Jakub Jelinek
2022-11-15 0:00 ` Jason Merrill
2022-11-15 8:54 ` Jakub Jelinek [this message]
2022-11-15 8:54 ` [PATCH] c++, v2: " Jakub Jelinek
2022-11-15 21:51 ` 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=Y3NTqLfSD5kwo1SD@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=jwakely@redhat.com \
--cc=ppalka@redhat.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).