Topic: Resumable Functions / Boost.Asio Stackless


Author: Evgeny Panasyuk <evgeny.panasyuk@gmail.com>
Date: Sat, 6 Jun 2015 14:03:30 -0700 (PDT)
Raw View
------=_Part_822_657984711.1433624610153
Content-Type: multipart/alternative;
 boundary="----=_Part_823_1110164148.1433624610159"

------=_Part_823_1110164148.1433624610159
Content-Type: text/plain; charset=UTF-8

I was told that there were discussion where exactly same concerns has been
articulated:
https://groups.google.com/a/isocpp.org/forum/#!topic/std-proposals/_ssbHm4C2t8
I.e. allocation, copy/move, serialization, value-typeness, etc.

Also I was told about Stackless Coroutines proposal N4244 by Christopher
Kohlhoff (author of Boost.Asio)
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4244.pdf which
follows same conception as in stackess coroutines macros from Boost.Asio.
N4244 describes coroutines which are better aligned with C++ idioms, more
lightweight and optimization-friendly than coroutines from N4134.
And as far as I can tell N4244 coroutines are strictly more powerful - they
can be copied/moved, per-member operations are easy to generate like
operator==/serialize (either by compile-time reflection or automatically by
compiler) enabling for example multi-pass generators or migration of
coroutines over network.

Best Regards,
Evgeny Panasyuk

--

---
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_823_1110164148.1433624610159
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I was told that there were discussion where exactly same c=
oncerns has been articulated:<br>https://groups.google.com/a/isocpp.org/for=
um/#!topic/std-proposals/_ssbHm4C2t8<br>I.e. allocation, copy/move, seriali=
zation, value-typeness, etc.<br><br>Also I was told about Stackless Corouti=
nes proposal N4244 by Christopher Kohlhoff (author of Boost.Asio) http://ww=
w.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4244.pdf which follows same=
 conception as in stackess coroutines macros from Boost.Asio.<br>N4244 desc=
ribes coroutines which are better aligned with C++ idioms, more lightweight=
 and optimization-friendly than coroutines from N4134.<br>And as far as I c=
an tell N4244 coroutines are strictly more powerful - they can be copied/mo=
ved, per-member operations are easy to generate like operator=3D=3D/seriali=
ze (either by compile-time reflection or automatically by compiler) enablin=
g for example multi-pass generators or migration of coroutines over network=
..<br><br>Best Regards,<br>Evgeny Panasyuk</div>

<p></p>

-- <br />
<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 <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 />
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_823_1110164148.1433624610159--
------=_Part_822_657984711.1433624610153--

.