Re: [boost] New dependency report

Le 09/06/14 00:46, Peter Dimov a écrit :

Andrey Semashev wrote

...

mpl::bool_ is not the only thing TypeTraits uses from MPL, so this dependency won't go that easily.

The list appears long, ...

http://www.pdimov.com/tmp/report-b932921/type_traits.html#mpl

... but most of the nontrivial metaprogramming is done by common_type. The other contenders are floating_point_promotion and detail/template_arity_spec. |The floating_point_promotion dependency is only if BOOST_NO_CV_SPECIALIZATIONS is defined. Do we support compiler defining this?

$ grep -r BOOST_NO_CV_SPECIALIZATIONS * boost/config/compiler/borland.hpp:# define BOOST_NO_CV_SPECIALIZATIONS boost/config/compiler/mpw.hpp:# define BOOST_NO_CV_SPECIALIZATIONS boost/config/suffix.hpp:# if defined(BOOST_NO_CV_SPECIALIZATIONS) \ The detail/template_arity_spec dependency more complex. from from from from If we had simplified version of integral_constant, conditional, and_, or_, boo_, int_ The following dependencies could be resolved from from from refactor integral_constant.hpp and bool_trait_def.hpp and to don't depend on mpl/bool.hpp, but on type_traits_core/integral_constant.hpp. from Define it independently of mpl/if.hpp. type_traits_core/conditional.hpp. from from from Refactor them to use conditional from from Make use directly of integral_constant or define a type_traits::int_<N> from Don't use any more intergral_c. Use type_traits_core/integral_constant.hpp from Add type_traits_core/not.hpp from Use type_traits_core/integral_constant.hpp There are yet these dependencies to resolve from from from from from from from from from |

The reverse,

http://www.pdimov.com/tmp/report-b932921/mpl.html#type_traits

looks breakable as well.

How do you want to break it? Duplicating what is used? Best, Vicente