Andrey Semashev wrote:
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.
No, it isn't silly at all. Silly is having a whole physical dependency on an entire repo just to have a one line macro. That's why C++11 libraries define their own instead of using StaticAssert. But then there's another silly thing. You define your own macro, but this just moves StaticAssert from a primary dependency to a secondary dependency because Core brings it in. We don't want silly things.