From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [C2x] Disallow function attributes after function identifier
Date: Sat, 11 Jun 2022 13:53:20 +0100 [thread overview]
Message-ID: <CAH6eHdSUnsYnv53F9vderj8v-qT1rLVH=15CyZc6rcdD=62-bQ@mail.gmail.com> (raw)
In-Reply-To: <ded635a8-6204-d088-e009-f9c3821f4b54@gmail.com>
On Sat, 11 Jun 2022, 10:00 Alejandro Colomar, <alx.manpages@gmail.com>
wrote:
> Hi Jonathan,
>
> On 6/11/22 00:47, Jonathan Wakely wrote:
> > Well, I'd argue the same reasons to remove it from C++. Don't know
> how
> > useful that feature is for C++, though. I bet not much, but am not
> an
> > expert in the language.
> >
> >
> > It's used in libstdc++ because I couldn't get an attribute to work in
> > any other location, because it isn't valid at other positions in a
> > constrained function template. So no, we can't remove it from C++.
> >
>
> Hmm, okay, not removable in C++. I'm curious about the specific line of
> code, if you have it around and could link to it. But C++ is huge, so
> anything is to be expected :)
>
https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=libstdc%2B%2B-v3/include/bits/ranges_base.h;h=38db33fd2ce9ea4c2a2a11035e09f41ba008515c;hb=HEAD#l111
prev parent reply other threads:[~2022-06-11 12:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 20:40 Alejandro Colomar
2022-06-10 21:09 ` Joseph Myers
2022-06-10 21:35 ` Alejandro Colomar
2022-06-10 21:16 ` Jakub Jelinek
2022-06-10 21:31 ` Alejandro Colomar
2022-06-10 22:47 ` Jonathan Wakely
2022-06-11 9:03 ` Alejandro Colomar
2022-06-11 12:08 ` Gabriel Ravier
2022-06-11 20:20 ` Alejandro Colomar
2022-06-13 15:54 ` Jonathan Wakely
2022-06-11 12:53 ` Jonathan Wakely [this message]
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='CAH6eHdSUnsYnv53F9vderj8v-qT1rLVH=15CyZc6rcdD=62-bQ@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.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).