--001a1133c3bc6671bd0510a36c03
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

>
> struct X
>  {
>      int x;
>      auto y;
>  };
>

Ermm... yikes, no. That's like saying that this is a template

void f()
{
  auto x =3D y;
}

because it has an auto.

I seem to recall some EWG papers or discussion about using auto as the type
of a member variable. I don't remember what the outcome was.

 (Again, I'm not actually against 'auto means template function'=E2=80=8E; =
I just
> bring up counter arguments to be comfortable that we explored the design
> space and that we have a path of consistency going forward)
>

I remember discussing these questions in Bjarne's office years ago... We
have explored in this direction, and here be dragons.

Andrew

--=20

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

--001a1133c3bc6671bd0510a36c03
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div bgcolor=3D"#FFFFFF"><div style=3D"width:100=
%;font-size:initial;font-family:Calibri,&#39;Slate Pro&#39;,sans-serif,sans=
-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255=
,255)"><span style=3D"font-size:initial;text-align:initial">struct X</span>=
<br></div>
<div style=3D"width:100%;font-size:initial;font-family:Calibri,&#39;Slate P=
ro&#39;,sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;backg=
round-color:rgb(255,255,255)">
{</div>
<div style=3D"width:100%;font-size:initial;font-family:Calibri,&#39;Slate P=
ro&#39;,sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;backg=
round-color:rgb(255,255,255)">
=C2=A0 =C2=A0 int x;</div>
<div style=3D"width:100%;font-size:initial;font-family:Calibri,&#39;Slate P=
ro&#39;,sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;backg=
round-color:rgb(255,255,255)">
=C2=A0 =C2=A0 auto y;</div>
<div style=3D"width:100%;font-size:initial;font-family:Calibri,&#39;Slate P=
ro&#39;,sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;backg=
round-color:rgb(255,255,255)">
};</div></div></blockquote><div><br></div><div>Ermm... yikes, no. That&#39;=
s like saying that this is a template</div><div><br></div><div>void f()</di=
v><div>{</div><div>=C2=A0 auto x =3D y;</div><div>}</div><div><br></div><di=
v>because it has an auto.</div><div><br></div><div>I seem to recall some EW=
G papers or discussion about using auto as the type of a member variable. I=
 don&#39;t remember what the outcome was.</div><div><br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><div bgcolor=3D"#FFFFFF">
<div style=3D"width:100%;font-size:initial;font-family:Calibri,&#39;Slate P=
ro&#39;,sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;backg=
round-color:rgb(255,255,255)">
(Again, I&#39;m not actually against &#39;auto means template function&#39;=
=E2=80=8E; I just bring up counter arguments to be comfortable that we expl=
ored the design space and that we have a path of consistency going forward)=
=C2=A0<span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-=
size:small;text-align:initial">=C2=A0</span></div></div></blockquote></div>=
<br></div><div class=3D"gmail_extra">I remember discussing these questions =
in Bjarne&#39;s office years ago... We have explored in this direction, and=
 here be dragons.</div><div class=3D"gmail_extra"><br></div><div class=3D"g=
mail_extra">Andrew</div></div>

<p></p>

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

--001a1133c3bc6671bd0510a36c03--

.

[dropping core]


On Fri, Mar 6, 2015 at 1:09 PM, Andrew Sutton <asutton.list@gmail.com> wrote:
>> struct X
>> {
>>     int x;
>>     auto y;
>> };
>
>
> Ermm... yikes, no. That's like saying that this is a template
>
> void f()
> {
>   auto x = y;
> }
>
> because it has an auto.
>
> I seem to recall some EWG papers or discussion about using auto as the type
> of a member variable. I don't remember what the outcome was.
>

http://www2.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3897.html

--

---
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/.

.