3 Jun
2014
3 Jun
'14
11:39 a.m.
On Tue, Jun 3, 2014 at 2:43 PM, Peter Dimov
Andrey Semashev wrote:
That is ok, if we decide that Boost.Core can depend on Boost.MPL.Core.
Because then blank.hpp will depend on mpl_core, and we won't be able to move it into core? True, unfortunately.
Otherwise there's not much point in such extraction as MPL doesn't have many dependencies itself.
Utility will go away as soon as we deal with value_init.hpp. Detail - when detail/endian.hpp is replaced with Predef. Config, PP, StaticAssert and TypeTraits are left. Not so bad already, almost all of them are valid dependencies of Core. TypeTraits might further be replaced with Core.TypeTraits. So what do you think, is it worth to split MPL?