From: Ville Voutilainen <ville.voutilainen@gmail.com>
To: Marek Polacek <polacek@redhat.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] g++, libstdc++: implement __is_nothrow_{constructible, assignable}
Date: Sat, 24 Oct 2020 03:11:29 +0300 [thread overview]
Message-ID: <CAFk2RUaZFhuzJ8Vzb0jzU9==fhfcQ1+HqrsmKx5zVGpjYfDDZA@mail.gmail.com> (raw)
In-Reply-To: <20201024000702.GR3628@redhat.com>
On Sat, 24 Oct 2020 at 03:07, Marek Polacek <polacek@redhat.com> wrote:
> > Ha, we have the same thing in is_trivially_xible, so I'll drive-by
> > change that one as well.
>
> Please. Thanks!
The tree is also on a separated line in is_trivially_xible and
is_nothrow_xible, but not
in is_xible. What do we think about line-whitespace changes mixed with
'real' changes?
next prev parent reply other threads:[~2020-10-24 0:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 23:32 Ville Voutilainen
2020-10-23 23:34 ` Ville Voutilainen
2020-10-24 0:00 ` Marek Polacek
2020-10-24 0:03 ` Ville Voutilainen
2020-10-24 0:07 ` Marek Polacek
2020-10-24 0:11 ` Ville Voutilainen [this message]
2020-10-24 15:41 ` Marek Polacek
2020-10-24 1:37 ` Jason Merrill
2020-10-26 12:22 ` Jonathan Wakely
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='CAFk2RUaZFhuzJ8Vzb0jzU9==fhfcQ1+HqrsmKx5zVGpjYfDDZA@mail.gmail.com' \
--to=ville.voutilainen@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=polacek@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).