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-23 12:30:41

On Thu, Aug 23, 2018 at 8:16 AM John Maddock wrote:
> That's sort of true - but we're talking about moving some of them only.

Right.

> Now at present the is_final and is_empty intrinsics have no workarounds,
> but I wouldn't rule them out in the future if say the Acme Devastator
> compiler's __is_final dies with some new C++30 compiler feature.

Sure. That scenario would be not very different for various other
compiler-specific macros maintained in Config, that may require (in
future) more compiler-specific workarounds, no? (e.g. BOOST_ALIGNMENT
could find itself in the same boat). (Possible, but unlikely, since
for an implementation to regress now with a broken std::is_final or a
broken alignas would be very crippling, but you never know...).

Glen
Glen