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

Subject: Re: [boost] [type_traits][core] modularisation and moving stuff about (again)
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2018-08-22 21:46:03

On Thu, Aug 23, 2018 at 12:38 AM, Glen Fernandes
<glen.fernandes_at_[hidden]> 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?