On Wed, Jan 22, 2014 at 1:54 PM, Vicente J. Botet Escriba
Le 22/01/14 17:07, Nat Goodspeed a écrit :
Moreover (a key point) anyone invoking the Fiber API who is constrained to C++03 features will not have movable-only types. In that scenario, fiber(bind(callable, arg1, arg2)) *is* completely equivalent to fiber(callable, arg1, arg2).
I disagree. We have Boost/Move.
Hmm, okay.
So when discussing the requested variadic fiber constructor, I will tease apart the C++11 and C++03 cases. I feel pretty comfortable stating that the former is much more important than the latter.
Agreed, but at least the C++03 must support movables types.
On seeing your response above, my impulse is to think you mean: "at least with a C++11 compiler, the fiber constructor must support movable types." Please clarify? If in fact you mean C++03, may we interpret that as: "if the Fiber library provides a C++03-compatible variadic fiber constructor, that constructor must support movable types" ?