Re: [boost] [type_traits][core] modularisation and moving stuff about (again)

Subject: Re: [boost] [type_traits][core] modularisation and moving stuff about (again)
From: Glen Fernandes (glen.fernandes_at_[hidden])
Date: 2018-08-22 22:36:52

On Wednesday, August 22, 2018, Andrey Semashev wrote:

> On Thu, Aug 23, 2018 at 12:38 AM, Glen Fernandes wrote:
> > On Wednesday, August 22, 2018, Andrey Semashev wrote:
> >>
> >> I think we should keep stuff where it belongs, if possible.
> >
> > I agree, in general. The reason we are moving the two macros
> BOOST_IS_FINAL
> > and BOOST_IS_EMPTY to Boost.Config is because it isn't possible. We want
> to
> > use them in Boost.Core and Boost.Core cannot depend on Boost.TypeTraits.
>
> Maybe we should make it possible to use Boost.TypeTraits in
> Boost.Core? I wasn't happy when we duplicated is_same, now this. I'm
> sure, we'll want more traits in time.
>
> Is the restriction of Boost.TypeTraits because it depends on Boost.MPL?
>

At one point in time. Since Core was established the criteria for for
inclusion in it has been "not dependent on any other Boost modules except
Core itself, Config, Assert, Static Assert, or Predef."

I suppose TypeTraits has changed sufficiently enough now to consider
relaxing that...

Glen