From: Jonathan Wakely <jwakely@redhat.com>
To: Ed Smith-Rowland <3dw4rd@verizon.net>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, libstdc++] Doc changes for constexpr additions for C++20 status.
Date: Mon, 09 Sep 2019 09:41:00 -0000 [thread overview]
Message-ID: <20190909094131.GU9487@redhat.com> (raw)
In-Reply-To: <6818b3ad-3e8a-2f49-30fc-ffc530a294d6@verizon.net>
On 05/09/19 15:45 -0400, Ed Smith-Rowland via libstdc++ wrote:
>Here is a patch to the libstdc++ docs re constexpr additions. They
>reflect the latest macro assignments AFAICT.
>
>Constexpr interator reqs are implemented in 9.1, the rest for 10.1.
>
>Ok?
>
>Should I bother adding the Constexpr interator requirements to the
>gcc-9 branch docs?
Yes please, it would be good to have that part in the gcc-9 docs. No
need to regen the HTML on the branch at this time though.
Thanks!
next prev parent reply other threads:[~2019-09-09 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 19:46 Ed Smith-Rowland via gcc-patches
2019-09-09 9:41 ` Jonathan Wakely [this message]
2019-09-09 17:25 ` Ed Smith-Rowland via gcc-patches
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=20190909094131.GU9487@redhat.com \
--to=jwakely@redhat.com \
--cc=3dw4rd@verizon.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=libstdc++@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).