public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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++@gcc.gnu.org
Subject: Re: [libstdc++ PATCH] More Fundamentals v1 variable templates
Date: Mon, 20 Oct 2014 12:43:00 -0000	[thread overview]
Message-ID: <20141020123801.GE3033@redhat.com> (raw)
In-Reply-To: <CAFk2RUbMvrj4i+YSMJLRmwvFvdoVEsApBGtYNWEH2JrpXhpvDA@mail.gmail.com>

On 18/10/14 23:22 +0300, Ville Voutilainen wrote:
>On 18 October 2014 23:18, Ville Voutilainen <ville.voutilainen@gmail.com> wrote:
>> Tested on Linux-x64.
>>
>> 2014-10-18  Ville Voutilainen  <ville.voutilainen@gmail.com>
>>
>>     Implement more Library Fundamentals v1 variable templates for
>>     type traits.
>>     * include/Makefile.am: Add ratio, chrono and system_error.
>>     * include/experimental/chrono: New.
>>     * include/experimental/ratio: Likewise.
>>     * include/experimental/system_error: Likewise.
>>     * include/experimental/tuple (tuple_size_v): Likewise.
>>     * testsuite/experimental/chrono/value.cc: Likewise.
>>     * testsuite/experimental/ratio/value.cc: Likewise.
>>     * testsuite/experimental/system_error/value.cc: Likewise.
>>     * testsuite/experimental/tuple/tuple_size.cc: Likewise.
>
>Hah, failed to uglify system_error. New patch attached.

Thanks.

The templates should also use 'typename' not 'class' but I can make
that change before committing it so no need for a new patch.

I'll do the commit tomorrow.

  reply	other threads:[~2014-10-20 12:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-18 20:23 Ville Voutilainen
2014-10-18 21:07 ` Ville Voutilainen
2014-10-20 12:43   ` Jonathan Wakely [this message]
2014-10-21  5:37     ` Ville Voutilainen
2014-10-21 13:21       ` 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=20141020123801.GE3033@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).