------=_Part_242_390341005.1470279104052
Content-Type: multipart/alternative;
 boundary="----=_Part_243_518082736.1470279104052"

------=_Part_243_518082736.1470279104052
Content-Type: text/plain; charset=UTF-8

Hi,

In Oulu, my proposal P0315R0 [1] for allowing lambdas in unevaluated
contexts
was discussed. However, due to incorrect wording, the intended effect of
allowing lambdas to appear in alias declarations & al would not have been
achieved. Furthermore, there was some fear that lambdas would be allowed to
appear in the signature of functions with external linkage if the wording
was changed as proposed. Hence, the paper was rejected.

I rewrote the wording of the paper to account for these defficiencies and I
would like to pass it through this list to see whether the new wording seems
OK with everyone. Please send any comments, here's the revised paper:

  https://github.com/ldionne/wg21/blob/master/pdf/P0315R1.pdf

Due credit: I was _greatly_ helped by Hubert Tong and David Vandervoorde in
the second iteration of this wording.

Regards,
Louis Dionne

[1]: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0315r0.pdf

--
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.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/00447307-d52f-4277-9a34-180f4c31a73b%40isocpp.org.

------=_Part_243_518082736.1470279104052
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,</div><div><br></div><div>In Oulu, my proposal P03=
15R0 [1] for allowing lambdas in unevaluated contexts</div><div>was discuss=
ed. However, due to incorrect wording, the intended effect of</div><div>all=
owing lambdas to appear in alias declarations &amp; al would not have been<=
/div><div>achieved. Furthermore, there was some fear that lambdas would be =
allowed to</div><div>appear in the signature of functions with external lin=
kage if the wording</div><div>was changed as proposed. Hence, the paper was=
 rejected.</div><div><br></div><div>I rewrote the wording of the paper to a=
ccount for these defficiencies and I</div><div>would like to pass it throug=
h this list to see whether the new wording seems</div><div>OK with everyone=
.. Please send any comments, here&#39;s the revised paper:</div><div><br></d=
iv><div>=C2=A0 https://github.com/ldionne/wg21/blob/master/pdf/P0315R1.pdf<=
/div><div><br></div><div>Due credit: I was _greatly_ helped by Hubert Tong =
and David Vandervoorde in</div><div>the second iteration of this wording.</=
div><div><br></div><div>Regards,</div><div>Louis Dionne</div><div><br></div=
><div>[1]: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0315r0.=
pdf</div><div><br></div></div>

<p></p>

-- <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 <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/00447307-d52f-4277-9a34-180f4c31a73b%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/00447307-d52f-4277-9a34-180f4c31a73b=
%40isocpp.org</a>.<br />

------=_Part_243_518082736.1470279104052--

------=_Part_242_390341005.1470279104052--

.