On 23 Oct 2025 03:51, Peter Dimov via Boost wrote:
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.
Again, then move the macro into Core or Config. Code duplication is not the answer. We have libraries to reuse code. If we're not using our own libraries, what does that tell us? BTW, I don't find adding a small dependency such as StaticAssert as a problem, assuming I really need it and C++11 static_assert is somehow not acceptable. But I actually have a hard time seeing how C++11 static_assert wouldn't cut it to such a degree that I would go an extra mile to define my own macro.