Il 13/06/2016 17:25, Thijs (M.A.) van den Berg ha scritto:
No not like that. I would think something different like this would add something to the table:
http://lists.boost.org/Archives/boost/2015/05/221948.php
Which basicly splits a container into a set of single type subcontainers. The problem I see with both a tuple_vector and a vector of boost::variant's is that the types that can be added to the containers are part of the declaration of the container, so you have to know them in advance. When this is possible IMO you approach is good. Density is addressing the case in which the declaration of the container can't depend on the type of elements. Think to the dense_function_queue. An element of this container may be the result of an std::bind, or a lambda, which are unnamed types.