My CppCon keynote went really well!
Fun times talking about new memory hierarchies and the best ways we can programmatically prepare for them in advance.
CppCon 2026 Volunteer training. A CoC exercise on a hypothetical incident of someone posting a photo of another without permission. This photo posted without permission.
Every Thursday immediately before CppCon, we invite members of the Denver C++ Meetup to join us for dinner at the Gaylord Rockies. (Note: Not everyone present is in the photo and not everyone in the photo was present.)
https://t.co/9Ilc0zyJp9
The arrangement with Karen Krueger and Aaron Robinson is that they do all the work on CppCon and I get all the credit. This arrangement has worked out really well for me.
The politics of the committee. The dedication of decades. The flow of solving the unsolvable, featuring some of "the brightest people you'll ever want to meet"
🎬 First audience preview screening
📅 September 16, 2026
📍 Exclusively for @CppCon attendees
https://t.co/YiShqOho5j
#cpp
"If I were to tell a story about Boost, I'd start with the people."
Today we're sharing the official teaser for the Boost documentary. A film about the people, the politics, and the decades of work behind possibly the most important open source library you've never heard of 🎥👇
std::vector always heap allocates. std::array can't change size. For decades, there's been no standard container that gives you a dynamically sized array with a compile-time capacity limit and zero heap allocation
C++26 finally adds std::inplace_vector. Guess where they got the idea 🧵👇
@MatRopert@blelbach@joaquintdig That double standard isn’t coming from me. Asio is arguably existing practice and, therefore, a candidate for ISO. But I’m not convinced that the benefit is worth the cost. There are benefits to leaving it in Boost.
@MatRopert@blelbach@joaquintdig The mandate of the committee is to standardize existing practice. For language features, this is problematic, but for libraries—nothing should go in that is not already in Boost (or a comparable source). The committee should fine-tuning not inventing.
@MatRopert@blelbach@joaquintdig I agree. We need to stop putting containers (or anything else that ages poorly) in the standard. But we also need to teach people the value of Boost and other premium resources.
@MatRopert@blelbach The standard has laid out the conventions that are the STL. It has a few (too many) containers, iterators, and algorithms. Now go forth and create your own. And if/when they are good enough, put them in Boost. The standard is the wrong place for every library that is a good idea.
I tried to stop std::hive.
When it became clear I couldn't, I tried to keep them for baking in a design that forced a particular implementation.
std::hive doesn't belong in the C++ standard library.