[boost] Re: BOOST_STATIC_ASSERT frowned up by core users

Andrey Semashev wrote:

Again, then move the macro into Core or Config.

Moving the macro to Core is stupid. If a library does not already depend on Core, it won't want to depend on Core, which is a heavier dependency. 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. I didn't see any benefits from not making it public. Libraries that already depend on Core can take advantage of it. boost/static_assert.hpp has a lot of baggage that is probably all obsolete, so having the leaner Core implementation available to others will be a good way to test that hypothesis, which will be useful for when we decide to move BOOST_STATIC_ASSERT to Config.