Am 06.10.2012 03:54, schrieb Rob Stewart:
On Oct 5, 2012, at 4:53 PM, Giovanni Piero Deretta <gpderetta@gmail.com> wrote:
On Fri, Oct 5, 2012 at 8:46 PM, Oliver Kowalke <oliver.kowalke@gmx.de>wrote:
Anyway, maybe the use of the get accessor can be made more readable without effort using tags does boost.tuple provide such a facility?
no, but boost.fusion does. Maybe coroutine should only support unary arguments/results and let the user choose its preferred "packaging" by explicitly specifying tuple or fusion map/sets?
+1
That would greatly simplify things. You wouldn't need to worry about signature inversion, the parameterization is streamlined, and accessing the argument can be reduced to an arg() accessor. coroutine<>::caller_t is a typedef of coroutine<> with inverted signature - you don't need to worry