We’re rolling full steam ahead into the future of Boost, and there’s never been a better time to get involved! Behind the scenes, we’ve been hard at work improving the appearance of our documentation to make exploring Boost more inviting and easier on the eyes. Whether you’re diving into a specific library or just browsing, things are looking better than ever. We’ve also given our release report a fresh touch. Beyond technical updates, we’re now shining a light on the amazing individuals wh...

My focus this quarter has been on drawing in C++ developers who are new to the Boost libraries. When I did my time at Microsoft, writing API documentation, THE most common question from the developer community was for sample code - more samples - better samples - samples with error handling - samples that are best practices. The easiest explanation of what is going on is so often a commented and runnable piece of sample code. To this end, I created - with help from AI - sample code for all o...

During Q1 2025, I’ve been working in the following areas: Candidate Boost Bloom Library During the entire quarter I’ve been working on a Boost proposal around Bloom filters: Repo: https://github.com/joaquintides/bloom Docs: https://master.bloom.cpp.al/ Class template boost::bloom::filter can be configured to implement a classical Bloom filter as well as variations discussed in the literature such as block filters, multiblock filters, and more. #include <boost/bloom/filter.hpp>...

Clang This quarter, I continued working on the fourth iteration of my refactoring of multi-level template argument list collection (#112381, #114258 and #114569 related), fixed support for the @relates command, made improvements to C++ conformance, amongst other things. Multi-level template argument list collection (again) My initial patch that refactored multi-level template argument list collection proved to have some nasty bugs relating to instantiation order. The following is a reducti...

The C++ Alliance supports both the great Boost Libraries and a current proposal for a memory/type/thread-safe version of C++ called Safe C++. They are not connected in any way other than the Alliance’s support. However, looking ahead, it seems smart for at least contributors to Boost to be aware of the progress and terminology of the Safe proposal. Before a contributor could do much the Safe C++ proposal would both have to be accepted and then implemented (super-easy to say and mountain of wo...