On 23 Oct 2025 03:32, Peter Dimov via Boost wrote:
Andrey Semashev wrote:
On 22 Oct 2025 06:37, Vinnie Falco via Boost wrote:
If you use BOOST_STATIC_ASSERT and you also use Boost.Core, you can use BOOST_CORE_STATIC_ASSERT instead and save one dependency.
Why do we keep adding this stuff to Core?? And even make it a public component, too?
To remove the dependency on StaticAssert.
I'm sorry, but this is just silly at this point. StaticAssert is even more lightweight than Core. If depending on it is a problem then how is it not a problem to depend on Core? And if you mean removing the dependency on it from Core, then why not merge StaticAssert into Core? Or into Config, which I think was suggested before? Or make it an internal implementation detail, if merging is not desirable for some reason? Why do we duplicate stuff in every library in the blind pursuit of reducing dependencies that doesn't bring any real benefits? How are users are supposed to know which alternative is the proper one? IMO, this component should be replaced with use of StaticAssert, which would in turn be merged in either Core or Config. Or, if not that, it should be made a private implementation detail of Core.