During Q2 2026, I’ve been working in the following areas: boost::container::hub The Boost official review took place April 16-26. The library was accepted as part of Boost.Container. Many thanks to the review manager, Ion Gaztañaga, and all the people who participated: Arnaud Becheler, Matt Bentley, Matt Borland, Dominique Devienne, Peter Dimov, Emil Dotchevski, Amlal El Mahrouss, Alexander Grund, Seth Heeren, Andrzej Krzemieński, Christian Mazakas, Andrey Semashev, Peter Turcan. During Ap...

The questions changed. For a long time, people asked about MrDocs in the abstract: what formats will it support, how will it handle templates, when will it be ready. Then, gradually, the questions became specific. Jean-Louis Leroy, the author of Boost.OpenMethod, became one of our most active sources of feedback. His library exercises corners of C++ that most projects never touch, which means MrDocs gets tested in ways we would not have anticipated. He wanted to know why his template speciali...

We had been putting off the Boost.URL security review for a while. There was always something more urgent. When the review finally happened, it confirmed what we hoped: the core parsing logic held up well. Around the same time, a constexpr feature request that we had been dismissing suddenly became a cross-library collaboration when other Boost maintainers started applying changes to their own libraries. And while working on Boost.Beast2 integration, we noticed friction in common URL operatio...

During Q1 2026, I’ve been working in the following areas: Boost.Container The rewritten boost::container::deque shipped in 1.90. Leaner container and iterators. Details and benchmarks against libstdc++, libc++ and MSVC STL on my blog: Inside Boost.Container: comparing different deque implementations. The deque implementation was refactored into a reusable deque_impl so it could back a new segtor container: a single-ended counterpart to deque (same segmented storage, push_back/pop_back only...

When new developers joined the MrDocs team, we expected the usual ramp-up: learning the codebase, understanding the architecture, and getting comfortable with the review process. What we did not expect was that building and testing the project would be the hardest part. People dedicated to the project full-time spent weeks just trying to get a working build. Even when they succeeded, each person ended up with their own set of workarounds: a custom script here, a patched flag there, an undocum...