AlisdairM wrote:
Thorsten Ottosen wrote:
I agree. I think this should go in the Array library, rather than boost.Assign.
Alisdair, do you agree?
It makes sense. I have thought about providing the functionality before, but didn't fancy getting on top of Boost PP to generate the overloads ;?)
I will certainly look into this as something to do for Boost 1.35.
Thanks Alisdair!
In my ideal world, this would be spelled as make_tuple though, and
Why? It seems to me that going through a tuple will force some copies, hence loose the efficiency.
tuples would be convertible to arrays. I don't think we can manage this in an acceptible manner without some changes to the initialization and POD rules.
Actually, we could probably add a conversion operator to the tuple template, to convert to arrays. I am not sure that is such a great idea though.
I don't have an opinion on this. -- Sylvain