Topic: Current state of "Accessors and views with lifetime
Author: paulpeet17@gmail.com
Date: Tue, 12 Sep 2017 09:56:11 -0700 (PDT)
Raw View
------=_Part_3544_1558857864.1505235371912
Content-Type: multipart/alternative;
boundary="----=_Part_3545_1611141690.1505235371912"
------=_Part_3545_1611141690.1505235371912
Content-Type: text/plain; charset="UTF-8"
Hey,
I came across this document discussing explicit/implicit lifetime extension
which sounds really interesting, especially the Polymorphic lifetime
analysis part.
Has there been any news about this proposal? The paper has some interesting
motivating examples where the current lifetime extension is quite limited.
One example in particular deals with "ranges", since I guess we could
expect ranges in C++20 (I really hope :)), I am wondering if it isn't right
to actually deal with this issue.
Best Regards,
Paul
P0066: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0066r0.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/816723f4-eaa5-4d81-9d21-5e2b3a7bc82a%40isocpp.org.
------=_Part_3545_1611141690.1505235371912
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hey,<div><br></div><div>I came across this document discus=
sing explicit/implicit lifetime extension which sounds really interesting, =
especially the=C2=A0Polymorphic lifetime analysis part.</div><div>Has there=
been any news about this proposal? The paper has some interesting motivati=
ng examples where the current lifetime extension is quite limited.</div><di=
v>One example in particular deals with "ranges", since I guess we=
could expect ranges in C++20 (I really hope :)), I am wondering if it isn&=
#39;t right to actually deal with this issue.</div><div><br></div><div>Best=
Regards,</div><div>Paul</div><div><br></div><div>P0066:=C2=A0http://www.op=
en-std.org/jtc1/sc22/wg21/docs/papers/2015/p0066r0.pdf</div></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" 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/816723f4-eaa5-4d81-9d21-5e2b3a7bc82a%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/816723f4-eaa5-4d81-9d21-5e2b3a7bc82a=
%40isocpp.org</a>.<br />
------=_Part_3545_1611141690.1505235371912--
------=_Part_3544_1558857864.1505235371912--
.