On 23 Oct 2025 04:55, Peter Dimov via Boost wrote:
Andrey Semashev wrote:
On 23 Oct 2025 04:40, Peter Dimov via Boost wrote:
Andrey Semashev wrote:
On 23 Oct 2025 04:16, Peter Dimov via Boost wrote:
Andrey Semashev wrote:
Again, then move the macro into Core or Config.
Moving BOOST_STATIC_ASSERT to Config is a good solution. Once it's done, we can retire BOOST_CORE_STATIC_ASSERT. Until then, it's necessary.
No, as that keeps the BOOST_CORE_STATIC_ASSERT duplicate, and potentially allows users to depend on it, only then to be removed.
Why do you want BOOST_CORE_STATIC_ASSERT right now?
Already answered in my first message.
You didn't. Not the "right now" part.
"Right now" doesn't affect my answer. The timing is arbitrary, as would be any delay.
If timing is not essential then let's do it the right way and save everyone from the deprecation of BOOST_CORE_STATIC_ASSERT. Let's revert the addition of BOOST_CORE_STATIC_ASSERT and then, after the release, merge BOOST_STATIC_ASSERT into Config.