M&M 2026Kitware is pleased to be returning to the Microscopy & Microanalysis (M&M) conference. This year, we will be exhibiting and hosting a vendor tutorial about the Tomviz 3.0 release. We also had a platform presentation accepted on our DOE Phase II-funded open source multivariate visualization work. Visit us at Booth #1222 to learn more, or contact our team to schedule a meeting.πKitware IncWelcome to SwedenCpp
Latest blogs, videos, podcasts and releases in one stream
Thursday, July 9, 2026
M&M 2026Kitware is pleased to be returning to the Microscopy & Microanalysis (M&M) conference. This year, we will be exhibiting and hosting a vendor tutorial about the Tomviz 3.0 release. We also had a platform presentation accepted on our DOE Phase II-funded open source multivariate visualization work. Visit us at Booth #1222 to learn more, or contact our team to schedule a meeting.πKitware Inc
Iβve decoded a #pragma detect_mismatch error and fixed the mismatch, but I still get the errorYou need to rebuild everything that was dependent on the change. The post Iβve decoded a #pragma detect_mismatch error and fixed the mismatch, but I still get the error appeared first on The Old New Thing .πThe Old New Thing
Refactoring Towards Structured Concurrencyπ₯CppOnline
Qt for MCUs 2.12.2 LTS ReleasedQt for MCUs 2.12.2 LTS has been released and is available for download. This patch release provides several bug fixes and other improvements while maintaining source compatibility with Qt for MCUs 2.12 (see Qt for MCUs 2.12 LTS released ). This release does not add any new functionality however as part of a continuous effort to scale Qt for MCUs to more platforms new Tier-2 board Nuvoton Gerda-4L is now available.πQt Blog
Whatβs New in vcpkg (June 2026)These June updates add a vcpkg-tool switch to skip installation when packages are already cached, OpenHarmony (OHOS) platform support, and major library updates including curl 8.21, CGAL 6.2, and Graphviz 15. The post Whatβs New in vcpkg (June 2026) appeared first on C++ Team Blog .πC++ Team BlogIf this page is useful, please consider donating a coffee
Wednesday, July 8, 2026
Modern GPU Programming with SDL3π₯Utah Cpp ProgrammersThe other kind of control flow guard check: The combined validate and callA two-in-one package. The post The other kind of control flow guard check: The combined validate and call appeared first on The Old New Thing .πThe Old New Thing
An Open Toolkit for Real-Time Audio Descriptors - Valerio Orlandini - ADC 2025π₯audiodevcon
OpenGL Textures - Application - Your first textured quad [Episode 42]π₯Mike Shah
pass by value and pass by pointer [C++ Shorts Lesson 17]π₯Mike Shah
The Language Belongs to the People Who Write ItThe Language Belongs to the People Who Write It C++ is a working language. It runs the engines and the pipelines and the quiet infrastructure underneath almost everything people depend on, usually without anyone noticing it is there. And for forty years it has grown from the people who use it. Someone hits a wall, builds the thing that gets them past it, and shares what they learned. That is where the language comes from. Not one room somewhere. The whole community that writes it every day. We think that is worth building for on purpose. Most of the work that shapes C++ happens in the open. The proposals, the debates about where things should go next, the record of who argued what, all public, and it has been for years. The trouble is that public and reachable turned out to be two different things. The archive is enormous and scattered, and keeping up with it has quietly become a skill of its own, the kind you only have time for if tracking C++ is already part of your job. Most working developers never get there. Not because anything is hidden. Because it is exhausting. So that is where we started. The mailing tools at wg21.org make the public record usable. Search across the papers instead of hunting through them one at a time. Sort and filter down to the ones that actually touch your work. Follow a thread without having to already know where it lives. It is not glamorous work and it is not meant to be. The whole idea is to take a layer away rather than add one. A developer in Lagos or Osaka or a spare bedroom anywhere should be able to see what is happening in C++ as easily as someone who has been going to meetings for twenty years. That is the gap good tooling closes, and closing it is how a language stays the property of the people who use it. It is the first piece. There is more coming, all of it aimed at the same thing from different directions: making it cheaper to take part, clearer to follow along, possible to go from curious to contributing without a decade of context first. More on that as it ships. Knowing what is happening now is only one way in, though, and not everyone starts there. Some people come to a community through its history, and Boost has a good one. Decades of libraries built by people who mostly never got seen for the work. We have been putting that story on film, a documentary about where Boost came from and who made it. It is a better place to start than you would expect, and a lot more human than the code makes any of it look. Others come through play. So we made a collectible card game out of the Boost libraries. Every library is a card. So are the authors, and the events anyone who has shipped software will recognize on sight, the QA reject that saves you at the last second, the PM back from a conference with a head full of ideas. It is fun first. Underneath the fun it is a surprisingly honest picture of how the ecosystem actually runs. Open source deserves to be celebrated the way other creative traditions are, with things you can hold and hand to a friend. If a card game is how someone first learns what Boost is, good. That counts. And then there is the most direct way in, which is to build. Boost is the Allianceβs flagship, it is open, and it is right there. Fix a bug. Review a library. Propose something and argue for it in daylight. The work is real and nobody is guarding the door. None of these sits above the others. Different people walk in through different ones and end up in the same place. If there is a single conviction under all of it, it is this. A language used by millions of people ought to be shaped by more than a handful of them. You do not get there by asking anyoneβs permission. You get there by lowering the barriers, one at a time, until taking part stops feeling like a privilege and starts feeling ordinary. Better search. Better tools. A door that is genuinely open. And none of it works without you. We mean that plainly, not as a flourish. The tools get better because people use them and tell us where they break. The community gets stronger every time someone shows up, reads a paper, joins a list, reviews somebodyβs library, says the thing everyone else missed. You do not need a title or a seat. You need the language you already write, and an opinion about where it should go. C++ is not finished and it is not fragile. It is a living thing, kept alive by the people who care about it, and there are far more of them than there are chairs in any room. That is the bet we are making. Come be part of it.πThe C++ Alliance
Bringing Safety to HEPBringing Safety to HEP High-Energy Physics software is routinely trusted with complex detector geometries spanning millions of volumes, critical tracking and reconstruction algorithms, and multi-day simulations running on the Grid. A single silent unit mismatch in a double can invalidate an entire analysis or produce detector geometry that is 10Γ the wrong size. This post shows how mp-units can bring compile-time safety to HEP codebases (including a dedicated HEP system of quantities and units) and how large projects like ATLAS can adopt it incrementally without requiring a big-bang rewrite.πmp-unitsTuesday, July 7, 2026
Propagating exceptions from destructors with std::exception_ptrA few weeks ago, I wrote about what happens when a destructor actually throws and why it is a dangerous idea. One of the readers commented that he was once in a situation where he had to propagate an exception from a destructor. But as a destructor cannot safely throw and it also cannot return any value, he needed a better solution. And that solution was std::exception_ptr. Letβs look into wh...πSandor Dargo's Blog
Celebrating 14 years of Meeting C++: Meeting C++ and C++ User Groupsπ₯MeetingCppHow did Windows 95 decide that a setup program ran?It used some heuristics. The post How did Windows 95 decide that a setup program ran? appeared first on The Old New Thing .πThe Old New Thing
Coordinate your threads with a barrier (example in C)π₯Jacob Sorber
How Music and Optimization Led Alan de Freitas to Open Sourceπ₯C++ Alliance
Keep It Tight: Restrict Variadic Templates Using C++20 ConceptsI previously wrote about C++20's Concepts. Today I would like to discuss another aspect of Concepts: how they help you to limit the data type of a variadic type-template parameter to a specific one for all datatypes in the set. For reference, these are my previous posts about C β¦πAndreasFertig.com
Bazel Q2 2026 Community UpdateAnnouncements BazelCon 2026 - details The Details at a Glance: What: BazelCon 2026 Where: Postillion Hotel & Convention Centre Amsterdam, Netherlands When: October 13β15, 2026 October 13th - Training Day October 14th & 15th - 2 Conference days filled with technical sessions, Birds of a Feather and networking with the best in the field. Get your ticket and find all the details via the BazelCon website ! For the most up to date BazelCon news and updates, follow the Bazel X account and the #bazelcon Bazel Slack channel. Call for Proposals This year, we received a tremendous 170 talk submissions! A huge thank you to everyone who took the time to submit a proposal. The Review Committee is already diligently reviewing them to curate the 2026 schedule. Speaker confirmations will be sent out on July 20th, and we will announce the schedule a few days later. If your submission isn't selected this year, we highly encourage you to apply again next time - and we sincerely applaud your willingness to share your stories with the community! BazelCon Training Day Following last yearβs success, we are bringing back Training Day right before the main conference. The schedule features two parallel tracks with four sessions each, allowing you to choose one session per time slot. You can select your sessions when you secure your BazelCon ticket on the website. Already registered? You can easily edit your existing registration to secure a spot in the trainings of your choice. Please Note: Seats are limited. If your plans change and you can no longer attend, please free up your spot so someone on the waitlist can take your place. Product Updates Upcoming Bazel releases Bazel 9.2.0 is expected to release on 2026-07-09. RC1 was released on 2026-06-25. Bazel 8.8.0 is expected to release on 2026-07-15. Please send cherry-pick PRs against the release-8.8.0 branch before the RC1 cutoff on 2026-07-08. Q2 releases 9.1.0 was released in April β26, followed by patch 9.1.1 . 8.7.0 was released in May β26. Community Corner Updates from the JetBrains* team: Bazel for CLion plugin updates Debug flags are no longer injected automatically by debug run configurations. If your build already includes debug symbols, this change shouldn't impact you; otherwise, check the details here: https://jb.gg/clwb-debug-docs . You can now switch configurations if the current source file is built under multiple configurations in your project. Additionally, when you start debugging, we'll automatically select the correct configuration to keep your code insight and debug session in sync. Developments in the Bazel plugin by JetBrains for IntelliJ IDEA, PyCharm and GoLand in 2026.1 Improved stability and less freezes: all known freezes caused by the Bazel plugin have been fixed. Sync performance improved, with overhead removed. Less spurious analysis cache invalidations. Better hot swap in JVM applications. Graceful cancellation for Bazel run and build. Bazel 9 compatibility. More readable build and sync progress in IDE output. Find more details on the plugin "What's New" page. In the upcoming 2026.2 version, the team is focusing on improved support for Bazel projects with Python and Go, in particular when opened in PyCharm and GoLand. Meetup.build events Check out the recaps of the latest Build meetups organised by EngFlow! EngFlow x Uber Amsterdam Build Meetup 2026: Scaling Builds - hosted in the Uber office, the attendees got to enjoy 6 talks on all things Build. Munich Bazel Build Meetup 2026: Tackling Supply Chain Security and Monorepo Scalability - the community met in the Salesforce offices for more great talks and knowledge sharing. Recordings of talks will soon be available to watch online. Keep an eye on meetup.build for next meetup announcements. Community created content Articles Remote Cache CDC: Reusing Bytes - by Tyler French @BuildBuddy Accessing external resources reliably with Bazel - by Alexey Tereshenkov @Tweag Building and running Bazel applications on AutoSD: Toolchains, containers, and recommended practices - by Bilal Elmoussaoui Mastering Your Frontend Build with Bazel: Testing - by Matti Bar-Zeev Mastering Your Frontend Build with Bazel: Consolidating Tests - by Matti Bar-Zeev A Practical Introduction to Bazel Persistent Workers - by Adin ΔebiΔ Cleaning up old Bazel patterns - by Adin ΔebiΔ Micro-Benchmarking Java with JMH and Bazel - by Somak Dutta Why Bazel is the Endgame for Build Systems - by The Coding Gopher Videos Introduction to the Bazel build system - by Florent Castelli, presented during Sweden Cpp Bazel for SONiC: What We've Learned and Contributed - by Borja Lorente @Aspect Build Bazel and Rust at OpenAI with David Zbarsky - by Aspect Build Resources GitHub repository: https://github.com/bazelbuild/bazel Releases: https://github.com/bazelbuild/bazel/releases Slack chat: https://slack.bazel.build Google group: bazel-discuss@googlegroups.com Special Interest Groups (SIG): Reach out the email(s) listed below if youβd like to be added to the SIG calendar invites. SIG Meeting frequency Point of contact Rules authors Every two weeks bazel-contrib@googlegroups.com Android app development Monthly ahumesky@google.com Bazel plugin for IntelliJ Monthly en@jetbrains.com Remote execution API working group Monthly chiwang@google.com Supply chain security / SBOM Weekly fwe@google.com Interested in learning about SIGs or starting a new one? Find more information on our website . Want to get your SIG listed? Please add it to the Community repository . Ideas, feedback, and submissions are welcome! Thank you for reading this edition! Let us know if youβd like to see any new information or changes in future community updates by reaching out to product@bazel.build. We look forward to hearing from you. Thanks, Google Bazel team * Copyright Β© 2026 JetBrains s.r.o. JetBrains and IntelliJ are registered trademarks of JetBrains s.r.o.πBazel BlogMonday, July 6, 2026
Beginner's Guide to C++26 Reflectionπ₯CppOnlineI opened a file with FILE_FLAG_DELETE_ON_CLOSE, but now I changed my mindYou can't change your mind, but you can do it a different way. The post I opened a file with FILE_ FLAG_ DELETE_ ON_ CLOSE , but now I changed my mind appeared first on The Old New Thing .πThe Old New Thing
C++ Weekly - Ep 540 - Creating New Types with C++26's Reflectionπ₯Jason Turner
Try to find an error! #javascript #programming #codingπ₯PVS-Studio
Workshop: Audio Plugin DSP in Practice - Jan Wilczek & Linus Corneliusson - ADC 2025π₯audiodevcon
C++ pointers [Learn C++ Shorts Lesson 16]π₯Mike ShahSunday, July 5, 2026
Driving Chaos - Virtual Analog Modelling of a Chaotic Circuit with Wave Digital Filters - ADC 2025π₯audiodevcon
BeCPP Symposium 2026 - Guy Davidson - Abstraction: The True Superpower of C++π₯BeCPP Users Group
How to Use AI for Programmingπ₯The Cherno
LLVM-snippy: An Instruction Sequence Generator. Part 2: Ibexπ₯Konstantin Vladimirov
Textures - theory [OpenGL Episode 41]π₯Mike Shah
Break MSVC and Clang with this one weird trick!A few weeks ago I came across some code that MSVC and Clang both rejected, but GCC accepted. The error messages are different in MSVC and Clang, so clearly I must have done something wrong, and GCC falsely accepts the code, right? I mostly minimized the code, and ended up with this. (Compiler Explorer link) struct S{}; template void foo(T) { (void)[] (U) consteval -> bool { return requires { 0 * T{}; }; }(0); } void bar() { foo(S{}); } In this post I will explain how I got here, what I think is going on with all 3 of these compilers, and allude to what Iβll be talking about in the next article after this one.πBraden++Saturday, July 4, 2026
Scene Editor | Alpha Preview | Pard Engineπ₯PardCode
std::string [Learn C++ Shorts Lesson 15]π₯Mike ShahFriday, July 3, 2026
Modern C++ for Embedded Systems - From Fundamentals To Real-Time Solutionsπ₯CppOnline
Master Linux Debugging: Essential GDB & System Toolsπ₯CppCon
How did we conclude that CcNamespace.dll was the ringleader of a group of DLLs that unloaded prematurely?Contextual clues. The post How did we conclude that CcNamespace.dll was the ringleader of a group of DLLs that unloaded prematurely? appeared first on The Old New Thing .πThe Old New Thing
Celebrating 14 years of Meeting C++!π₯MeetingCpp
Perfect Oscillators in Less Than One Clock Cycle - Angus Hewlett - ADC 2025π₯audiodevcon
Sergei Blinov β Least Frequently Used Cache β 25.06.2026.π₯cppserbia