Topic: Consistency: TransformationTraits Redux v2 and std::tuple_element


Author: gonzalobg88@gmail.com
Date: Tue, 15 Oct 2013 00:55:49 -0700 (PDT)
Raw View
------=_Part_60_28720694.1381823749750
Content-Type: text/plain; charset=ISO-8859-1

I've been using TransformationTraits Redux v2 _t template aliases for a
while and they are so handy that those places in which they are not
available start feeling alien (e.g. std::tuple_element in std::tuple).

Would it also make sense to add a template alias for std::tuple_element
(e.g. std::tuple_element_t) such that one can use it without typename
....::type?

Are there any other places outside <type_traits> in which it would also
make sense to add these template aliases?

Of course, his would have to go in a different proposal targeted at C++1y.

Bests,
Gonzalo BG


--

---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.

------=_Part_60_28720694.1381823749750
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I've been using TransformationTraits Redux v2 _t template =
aliases for a while and they are so handy that those places in which they a=
re not available start feeling alien (e.g. std::tuple_element in std::tuple=
). &nbsp;<div><br></div><div>Would it also make sense to add a template ali=
as for std::tuple_element (e.g. std::tuple_element_t) such that one can use=
 it without typename ...::type?&nbsp;</div><div><br></div><div>Are there an=
y other places outside &lt;type_traits&gt; in which it would also make sens=
e to add these template aliases?</div><div><br></div><div>Of course, his wo=
uld have to go in a different proposal targeted at C++1y.</div><div><br></d=
iv><div>Bests,</div><div>Gonzalo BG</div><div><br></div><div><br></div></di=
v>

<p></p>

-- <br />
&nbsp;<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.<br />
To post to this group, send email to std-proposals@isocpp.org.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />

------=_Part_60_28720694.1381823749750--

.


Author: =?ISO-8859-1?Q?Daniel_Kr=FCgler?= <daniel.kruegler@gmail.com>
Date: Tue, 15 Oct 2013 10:34:42 +0200
Raw View
2013/10/15  <gonzalobg88@gmail.com>:
> I've been using TransformationTraits Redux v2 _t template aliases for a
> while and they are so handy that those places in which they are not
> available start feeling alien (e.g. std::tuple_element in std::tuple).
>
> Would it also make sense to add a template alias for std::tuple_element
> (e.g. std::tuple_element_t) such that one can use it without typename
> ...::type?

Yes, very much so.

> Are there any other places outside <type_traits> in which it would also make
> sense to add these template aliases?

Feel free to make a survey ;-)

- Daniel

--

---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.

.


Author: Cassio Neri <cassio.neri@gmail.com>
Date: Tue, 15 Oct 2013 05:02:24 -0700 (PDT)
Raw View
------=_Part_211_1247466.1381838545051
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable



On Tuesday, October 15, 2013 9:34:42 AM UTC+1, Daniel Kr=FCgler wrote:
>
>
> Feel free to make a survey ;-)=20
>
>
By the way, what happened to the traits that are not transformation? I=20
mean, in n3655<http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n365=
5.pdf>it's said that=20

LWG=92s request[ed] that aliases for ::type members be consistently provide=
d=20
for all the type traits, not only for those classified as=20
TransformationTraits.

(e.g., is_void_t, is_integral_t, etc.) AFAIK n3655<http://www.open-std.org/=
jtc1/sc22/wg21/docs/papers/2013/n3655.pdf>was adopted but these traits are =
not part of=20
n3690 <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3690.pdf>.=
=20
So, what happened?

Thanks,
Cassio.

--=20

---=20
You received this message because you are subscribed to the Google Groups "=
ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposa=
ls/.

------=_Part_211_1247466.1381838545051
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><br>On Tuesday, October 15, 2013 9:34:42 AM UTC+1, Dan=
iel Kr=FCgler wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0;ma=
rgin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><br>Feel f=
ree to make a survey ;-)
<br>
<br></blockquote><div><br>By the way, what happened to the traits that are =
not transformation? I mean, in <a href=3D"http://www.open-std.org/jtc1/sc22=
/wg21/docs/papers/2013/n3655.pdf">n3655</a> it's said that <br><br><div sty=
le=3D"margin-left: 40px;">LWG=92s request[ed] that aliases for ::type membe=
rs be consistently provided for all the type traits, not only for those cla=
ssified as TransformationTraits.<br></div><br>(e.g., is_void_t, is_integral=
_t, etc.) AFAIK <a href=3D"http://www.open-std.org/jtc1/sc22/wg21/docs/pape=
rs/2013/n3655.pdf">n3655</a> was adopted but these traits are not part of <=
a href=3D"http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3690.pdf=
">n3690</a>. So, what happened?<br><br>Thanks,<br>Cassio.<br></div></div>

<p></p>

-- <br />
&nbsp;<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.<br />
To post to this group, send email to std-proposals@isocpp.org.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />

------=_Part_211_1247466.1381838545051--

.


Author: =?ISO-8859-1?Q?Daniel_Kr=FCgler?= <daniel.kruegler@gmail.com>
Date: Tue, 15 Oct 2013 14:24:14 +0200
Raw View
2013/10/15 Cassio Neri <cassio.neri@gmail.com>:
> By the way, what happened to the traits that are not transformation? I me=
an,
> in n3655 it's said that
>
> LWG=92s request[ed] that aliases for ::type members be consistently provi=
ded
> for all the type traits, not only for those classified as
> TransformationTraits.
>
> (e.g., is_void_t, is_integral_t, etc.) AFAIK n3655 was adopted but these
> traits are not part of n3690. So, what happened?

There came a severe protest from the project editor at that time and
LWG reconsidered this adoption, so the formal motion passed was "Move
we apply N3655 (excluding part 4)".

- Daniel

--=20

---=20
You received this message because you are subscribed to the Google Groups "=
ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposa=
ls/.

.