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.
What is the urgency that you want to add it before moving BOOST_STATIC_ASSERT into Config?
BOOST_STATIC_ASSERT hasn't moved into Config for many years now.
Then, apparently, depending on StaticAssert wasn't such a big deal. If it is now then let's move it. After the release.