From: Marc Glisse <marc.glisse@inria.fr>
To: Jason Merrill <jason@redhat.com>
Cc: Marek Polacek <polacek@redhat.com>,
gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: C++ PATCH for C++17 class template placeholders
Date: Wed, 05 Oct 2016 14:47:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1610051634240.3271@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <CADzB+2=PAohrSsFWbP8kayG2uSBiabi8FmRhjq=vTN53-eJAjQ@mail.gmail.com>
On Wed, 5 Oct 2016, Jason Merrill wrote:
> On Wed, Oct 5, 2016 at 5:29 AM, Marek Polacek <polacek@redhat.com> wrote:
>> On Wed, Oct 05, 2016 at 08:58:08AM +0200, Marc Glisse wrote:
>>> On Tue, 4 Oct 2016, Jason Merrill wrote:
>>>
>>>> C++17 adds the ability to omit the template arguments for a class
>>>> template when declaring a variable with an initializer, much like auto
>>>> but supporting a wider variety of initialization. This is intended to
>>>> replace functions like make_tuple.
>>>
>>> Nice. Is there a macro to test for this feature? I couldn't find it in the
>>> latest sg10 list.
>>
>> And in a similar vein, is there a macro for Selection statements with
>> initializer? Can't find it anywhere.
>
> Not currently, for either. The rationale for not defining macros for
> some features is that for convenience features like this, anyone
> concerned about portability will just write code the old way.
Thanks. Sadly, this ignores the case of a library that wants to provide an
explicit deduction guide for its own types to progressive users compiling
with a C++17 compiler, without preventing C++14 users from using the
library the old way.
--
Marc Glisse
next prev parent reply other threads:[~2016-10-05 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 20:42 Jason Merrill
2016-10-05 3:12 ` Jason Merrill
2016-10-05 18:59 ` Jason Merrill
2016-10-05 6:58 ` Marc Glisse
2016-10-05 9:29 ` Marek Polacek
2016-10-05 14:05 ` Jason Merrill
2016-10-05 14:47 ` Marc Glisse [this message]
2016-10-05 14:50 ` Jason Merrill
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=alpine.DEB.2.20.1610051634240.3271@laptop-mg.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--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).