From: Jonathan Wakely <jwakely@redhat.com>
To: Ville Voutilainen <ville.voutilainen@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [v3 PATCH] Implement D0013R2, logical type traits.
Date: Thu, 12 Nov 2015 13:41:00 -0000 [thread overview]
Message-ID: <20151112134124.GB2937@redhat.com> (raw)
In-Reply-To: <CAFk2RUbEU2dv7eUQ5HxBBS2OoSShecS3RqZuwo8mPEyZZbXfSA@mail.gmail.com>
On 12/11/15 00:46 +0200, Ville Voutilainen wrote:
>On 12 November 2015 at 00:18, Jonathan Wakely <jwakely@redhat.com> wrote:
>> So I think we want to define them again, independently, in
>> <experimental/type_traits>, even though it might lead to ambiguities
>
>Here. Tested again on Linux-PPC64.
>
>2015-11-11 Ville Voutilainen <ville.voutilainen@gmail.com>
>
> Implement D0013R2, logical type traits.
>
> /libstdc++-v3
> * include/experimental/type_traits (conjunction, disjunction,
> negation, conjunction_v, disjunction_v, negation_v): New.
> * include/std/type_traits (conjunction, disjunction, negation):
> Likewise.
> * testsuite/20_util/declval/requirements/1_neg.cc: Adjust.
> * testsuite/20_util/make_signed/requirements/typedefs_neg.cc: Likewise.
> * testsuite/20_util/make_unsigned/requirements/typedefs_neg.cc:
> Likewise.
> * testsuite/experimental/type_traits/value.cc: Likewise.
> * testsuite/20_util/logical_traits/requirements/explicit_instantiation.cc:
>New.
> * testsuite/20_util/logical_traits/requirements/typedefs.cc: Likewise.
> * testsuite/20_util/logical_traits/value.cc: Likewise.
>
> /testsuite
> * g++.dg/cpp0x/Wattributes1.C: Adjust.
OK for trunk, thanks.
prev parent reply other threads:[~2015-11-12 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 22:06 Ville Voutilainen
2015-11-11 22:18 ` Jonathan Wakely
2015-11-11 22:46 ` Ville Voutilainen
2015-11-12 13:41 ` 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=20151112134124.GB2937@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=ville.voutilainen@gmail.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).