This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [v3] constexpr tuple

From: Marc Glisse <marc dot glisse at inria dot fr>
To: Christopher Jefferson <caj21 at st-andrews dot ac dot uk>
Cc: Paolo Carlini <paolo dot carlini at oracle dot com>, Daniel Krügler <daniel dot kruegler at googlemail dot com>, Benjamin Kosnik <bkoz at redhat dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, "libstdc++ at gcc dot gnu dot org" <libstdc++ at gcc dot gnu dot org>
Date: Thu, 8 Sep 2011 21:04:17 +0200 (CEST)
Subject: Re: [v3] constexpr tuple
References: <20110906172309.2e1aafb9@shotwell> <CAGNvRgAfGX0B4tDaHc72UgBSgqkCtD7Vbz-w-7qZ_+n3-V2tZw@mail.gmail.com> <4E68FCBC.2050301@oracle.com> <97E85212-2169-453E-90DF-40FB3D9DA057@st-andrews.ac.uk>
Reply-to: libstdc++ at gcc dot gnu dot org

On Thu, 8 Sep 2011, Christopher Jefferson wrote:

This might be totally insane, but I believe that:

tuple_cat(tuple_cat(A,B), C) always equivalent to tuple_cat(A,B,C);

That's a fine way to find the return type, but for code, doesn't it generate many copies? I think I'd forward_as_tuple and use some magic indices to extract everything at once.

--
Marc Glisse

Follow-Ups:
- Re: [v3] constexpr tuple
  - From: Marc Glisse

References:
- [v3] constexpr tuple
  - From: Benjamin Kosnik
- Re: [v3] constexpr tuple
  - From: Daniel Krügler
- Re: [v3] constexpr tuple
  - From: Paolo Carlini
- Re: [v3] constexpr tuple
  - From: Christopher Jefferson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]