Subject: Re: [boost] [type_traits][core] modularisation and moving stuff about (again)
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2018-08-23 11:33:48
On 08/23/18 14:28, Glen Fernandes wrote:
> On Thu, Aug 23, 2018 at 7:22 AM Andrey Semashev wrote:
>> I gathered that you intended to use BOOST_IS_FINAL as a way to access a
>> compiler intrinsic, i.e. use it in place of the type trait.
> Either in place of, or in addition to (doesn't matter to me) but not
> the type trait alone. Because the trait alone is inadequate, as I
> mentioned before.
Then it looks like everything's already in place in Boost.TypeTraits.
Why not just use it?
(Yes, I remember about circular dependencies; we can solve those,
although I don't see it as that much of a problem as the dependency on
Boost.MPL would have been.)
>> I didn't find those macros documented. Specifically for BOOST_IS_FINAL,
>> it is mentioned as a *way to detect* whether `boost::is_final` gives the
>> actual result and not just `false`. The docs don't say that
>> BOOST_IS_FINAL is a way to access compiler intrinsics, so if someone is
>> using it this way, he is relying on implementation details.
> They're documented here:
Ok, I missed this page, thanks.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk