id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
1404	Unordered Fusion Map constructors.	Dean Michael Berris <mikhailberis@…>	Joel de Guzman	"Currenty, when constructing Fusion Maps, the order of type arguments used as template parameters need to be followed in the constructor as well.

Example:

{{{

struct tags {
  struct type_1 { };
  struct type_2 { };
};

using namespace boost::fusion ;

typedef map< pair<tags::type_1, int>, pair<tags::type_2, int> > my_map_type ;

{
  // following line will not compile, because of the argument ordering
  my_map_type instance( make_pair<tags::type_2>(2), make_pair<tags::type_1>(1) );

  // following line will compile, because the argument order is the same as
  // the order of elements in the fusion map specialization
  my_map_type instace_works( make_pair<tags::type_1>(1), make_pair<tags::type_2>(2) );

}

}}}

The feature request is to support arbitrary ordering of constructor arguments, not necessarily to follow the order of argument types as prescribed in the template arguments to the fusion map.
"	Feature Requests	new	To Be Determined	fusion	Boost Development Trunk	Cosmetic