On 24 Oct 2025 16:25, Peter Dimov via Boost wrote:
Ion Gaztañaga wrote:
I'd really like to see BOOST_ASSERT in Config and have Boost.StaticAssert just include that header. Either we want to fine-grained organisation of parts and leave it in its own library, or we want no duplication. Either way we should act consistently to that even if that involves cloning another, small library. With --depth=1 this should be rather fast.
Well. I would say that ideally Boost.StaticAssert should just go once Boost.Config includes BOOST_STATIC_ASSERT and ports tests/doc to the Config repo. Users won't notice anything because Boost.Config will provide <boost/static_assert.hpp> when Boost.StaticAssert goes away. Or am I missing something?
It should probably remain so that boost.org/libs/static_assert keeps working, but the header doesn't need to be there, it would move to Config.
It should remain as long as other Boost libraries refer to static_assert submodule, but once they are updated it can be removed.