Am 07.01.26 um 15:56 schrieb Peter Dimov via Boost:
If I change depinst.py to properly "know" that boost/static_assert.hpp is now in Config, a lot of things break. That's because many libraries list StaticAssert as a dependency in their build.jam and CMakeLists.txt files, and since it's no longer used, depinst doesn't install it and there are errors.
We could in principle go over all these (there are ~54 of them) and fix them, but in my experience, changes that break things internally for us also usually break things for others as well.
So... instead, we could name the Config header boost/config/static_assert.hpp, leave boost/static_assert.hpp in StaticAssert, and have it include the Config one. So all code that used `boost/static_assert.hpp` would either need to be updated or still use Boost.StaticAssert? Doesn't sound like an improvement to me.
I don't see how we could break others: They'd continue to use StaticAssert if they are not aware of this change. If they adapt their tooling they have to special case/change that too. Also boost/config/static_assert.hpp doesn't seem to be the right place judging by existing headers. We have boost/cstdint and boost/limits there, not in boost/config and static_assert is similar to those not to the other configuration stuff. So I'd use `boost/static_assert.hpp` Best, Alex