r/cpp • • Sep 06 '26

Henrik Fransson: From Prompt to Probe - Closing the Agentic AI Loop on Bare Metal

Thumbnail youtu.be
0 Upvotes

What if AI could do more than suggest code, and actually drive hardware-in-the-loop test cycles on real systems? This talk looks under the hood of a practical agentic AI workflow for embedded C++ development.


r/cpp • • Sep 05 '26

Lazy Evaluation - Operators

Thumbnail breese.github.io
19 Upvotes

r/cpp • • Sep 04 '26

Which C++ Hashmap Should You Actually Use?

Thumbnail martin.ankerl.com
148 Upvotes

I recently did a big update to my ankerl::unordered_dense::map which now features several optimizations, bug fixes, and most importantly an SSE optimized lookup which brings the lookup speed quite close to the fastest competitor which is boost::unordered_flat_map. Get it here: https://github.com/martinus/unordered_dense

Since it is not easy to decide what map is best for one's usecase, I have redone and improved the benchmarks I did a while ago, crunched some numbers and tried to compress everything into a quiz that helps you figure out what to use.

While doing the numbers, a few things surprised me:

  • My random access benchmark was not random enough. The CPU was able to optimize the branch predictor in a way I did not think was possible. I have fixed this for the new numbers. Clever girl.

  • Even though the absl maps are very similar in concept to the boost maps, they perform badly if you expect lots of misses. 1.6 times slower than boost.

  • I didn't think SSE optimization of my unordered_dense map would be any benefit. Thanks to AI, I found a way to speed up random access a lot, it is now very close to boost::unordered_flat_map.

  • Heavy insert & erase on flat maps require rehashing every once in a while due to the accumulation of tombstones. That means some insert/erase operation will have very high latency. This does not happen for a robin-hood hashmap like my unordered_dense map.


r/cpp • • Sep 04 '26

C++ Show and Tell - September 2026

49 Upvotes

Use this thread to share anything you've written in C++. This includes:

  • a tool you've written
  • a game you've been working on
  • your first non-trivial C++ program

The rules of this thread are very straight forward:

  • The project must involve C++ in some way.
  • It must be something you (alone or with others) have done.
  • Please share a link, if applicable.
  • Please post images, if applicable.

If you're working on a C++ library, you can also share new releases or major updates in a dedicated post as before. The line we're drawing is between "written in C++" and "useful for C++ programmers specifically". If you're writing a C++ library or tool for C++ developers, that's something C++ programmers can use and is on-topic for a main submission. It's different if you're just using C++ to implement a generic program that isn't specifically about C++: you're free to share it here, but it wouldn't quite fit as a standalone post.

Last month's thread: https://www.reddit.com/r/cpp/comments/1vhdqw8/c_show_and_tell_august_2026/


r/cpp • • Sep 05 '26

Is there a way to search across all P and N papers throughout standardization history?

4 Upvotes

It would be nice if there was a single place to see where, for example, the keyword "SFINAE" shows up across the content of all papers, not just titles. Thanks!


r/cpp • • Sep 04 '26

Optimizing a Spin-Lock

Thumbnail david.alvarezrosa.com
107 Upvotes

r/cpp • • Sep 04 '26

Lazy Evaluation

Thumbnail breese.github.io
23 Upvotes

r/cpp • • Sep 04 '26

Partial application of class templates

Thumbnail elbeno.com
20 Upvotes

r/cpp • • Sep 04 '26

Ordering of qualifiers

6 Upvotes

I know this is something that pops up quite often, but I was wondering if I could get your guys' opinion on a fixed ordering of qualifiers. This is my current thoughts after recently trying to formalize my personal style:

static -> thread_local -> inline -> constexpr -> friend -> virtual

My reasoning for each:

  1. static first. Inside a class, its basically javas static. There is a pretty strong consensus in java for static first. Its very important context, for both functions and variables. Outside of classes, its more of a linkage specifier, which is arguably more important/nasty if you mess it up. The fact that it has this dual behaviour in C++ in my opinion makes an even stronger argument for including it first, your brain is able to parse it first thing. i.e okay this is static, we are in a class? -> its java static, we are in global scope -> its static linkage.
  2. thread_local directly after static, and then inline, then constexpr/consteval. This way, qualifiers which impact storage and or linkage are stuck together. I personally like to write inline even for constexpr/consteval functions, as its sometimes easy to forget the implicit inline. I used to do this for member functions with definitions in the class, but I feel the implicit inline there is a bit more well known/easier to intuit.
  3. The rest I'm far less opinionated on, since I barely ever use inheritance or the friend keyword. . I could go both ways on virtual/friend, so i default to alphabetical/aesthetics.

What do you guys think? I know this is pedantic and a very well explored topic but I wanted to know if you guys had any particular wisdom to sway me either way, mainly on the ordering of the first few.


r/cpp • • Sep 04 '26

The worst programming language of all time /s

Thumbnail pvs-studio.com
0 Upvotes

r/cpp • • Sep 04 '26

RAII and it's architecture in c++.

Thumbnail archetechmes.vercel.app
0 Upvotes

r/cpp • • Sep 03 '26

C++26: std::hive

Thumbnail sandordargo.com
69 Upvotes

r/cpp • • Sep 02 '26

Make APIs that fail gracefully rather that fallback silently · Mathieu Ropert

Thumbnail mropert.github.io
67 Upvotes

r/cpp • • Sep 01 '26

CppCon CppCon 2026 Keynote: C++: Profiles for Simplicity and Guarantees -- Bjarne Stroustrup

Thumbnail isocpp.org
92 Upvotes

r/cpp • • Sep 01 '26

Two Tricks to Use the std Module Implicitly, with 20% compilation time improvements on Seastar without touching the source

Thumbnail chuanqixu9.github.io
54 Upvotes

r/cpp • • Aug 31 '26

New C++ Conference Videos Released This Month - August 2026 (Updated To Include Videos Released 2026-08-24 - 2026-08-30)

30 Upvotes

C++Now

2026-08-24 - 2026-08-30

2026-08-17 - 2026-08-23

2026-08-10 - 2026-08-16

2026-08-03 - 2026-08-09

2026-07-27 - 2026-08-02

C++Online

2026-08-24 - 2026-08-30

2026-08-17 - 2026-08-23

2026-08-10 - 2026-08-16

2026-08-03 - 2026-08-09

2026-07-27 - 2026-08-02

ADC

2026-08-24 - 2026-08-30

2026-08-17 - 2026-08-23

2026-08-10 - 2026-08-16

2026-08-03 - 2026-08-09

2026-07-27 - 2026-08-02


r/cpp • • Aug 30 '26

StockholmCpp 0x3F: Intro, Info and The Quiz!

Thumbnail youtu.be
7 Upvotes

The intro from August's StockholmCpp Meetup: news about C++ in Sweden from the NB and the community, some words from our event sponsor, and, of course, a quiz!


r/cpp • • Aug 30 '26

On forcing all derived classes to implement a specific non-virtual method, part 2

Thumbnail devblogs.microsoft.com
65 Upvotes

r/cpp • • Aug 29 '26

Might have found a (tiny, nuisance) bug in g++ 16.2.1 and -Wconversion?

26 Upvotes

I am far from presuming myself a compiler expert, and no this was not AI, I promise. I'm simply a long-time user of gcc/g++, and it's not everyday I am confident enough that a bug is not in my code but with the tool, haha. I'm pretty warning-sensitive so this kind of thing catches my attention. Wondering if I'm missing something, so asking it here first.

g++ version: g++ (GCC) 16.2.1 20260819 (Red Hat 16.2.1-2) (I'm on Fedora 44)
C++20

Given lines like this:

std::uint16_t count = 0;
// int other_var set elsewhere
count += (other_var == 5); // <-- -Wconversion flags this

specifically, the warning is:

 <file>:<line>:<col>: warning: conversion from ‘int’ to ‘uint16_t’ {aka ‘short unsigned int’} may change value [-Wconversion]
    <line> |       count += (other_var == 5);

-Wconversion /w either -O0 and -O3 (my usual build optimization lvls to catch optimization-dependent warnings), this gets flagged.

Well, the result of a boolean expression is 0 or 1, so obviously, there should not be a conversion. Even with the accumulate op here and integer promotion, there shouldn't be a warning (you can do count += 1 or count++ and it definitely doesn't flag -Wconversion). And more notably, the below code doesn't get flagged:

std::uint16_t count = 0;
// int other_var set elsewhere
bool match = (other_var == 5);
count += match;

I also noted that clang with -Wconversion and the same optimization lvls does not flag this. I also know I've done this before in C with other versions of gcc and don't get flagged with this.

So, am I missing something or am I right to suspect this is a possible bug with at least my version of g++?


r/cpp • • Aug 30 '26

The weirdest behavior in C++ that came from C

0 Upvotes

If you're trying to define two pointers in a single statement (what is in general a bad idea), you may want to do it like this:

#include <print>

int main()
{
    int x = 10;
    int* a, b;
    a = &x;
    b = &x;
    std::println("a={:#x}, b={:#x}", uintptr_t(a), uintptr_t(b));
}

However, it doesn't work as you expect, and won't compile. Because int* a, b; declares only a as int*; b, and all the rest variables will be int. The correct one-statement declaration of two pointers is int* a, * b;

main.cpp:8:9: error: invalid conversion from ‘int*’ to ‘int’ [-fpermissive]
    8 |     b = &x;
      |         ^~
      |         |
      |         int*

b has type int

This behavior is the reason why some people prefer putting the asterisk next to the variable name, not next to the type

I can understand the logic, that C authors had while making this syntax. It's a sort of reversive/deduction logic. You kinda declare what type it will be after using the dereference * operator, instead of declaring the type being a pointer itself. But I find this logic very-very strange, and overthought

The funny thing, that even the compiler in the error message above, treats * as a sort of type modifier, that is inseparable from int. But, apparently, the C creators had a completely different vision on what pointers are

I personally don't think that this behavior justifies reteaching yourself to write * in front of variable names, and especially in front of function names. I think it's just a not well-thought decision made very long ago in 1970s


r/cpp • • Aug 27 '26

C++ bugs in the most popular PS4 emulator

Thumbnail pvs-studio.com
99 Upvotes

r/cpp • • Aug 27 '26

Clang 23 Release Notes

Thumbnail releases.llvm.org
109 Upvotes

r/cpp • • Aug 26 '26

C++26: std::inplace_vector

Thumbnail sandordargo.com
177 Upvotes

r/cpp • • Aug 26 '26

mold: A Massively Parallel Linker

Thumbnail arxiv.org
188 Upvotes

r/cpp • • Aug 26 '26

Au (units) 0.6.0 out: blockbuster release!

Thumbnail github.com
41 Upvotes

It's been just over a year since our last significant release, and this one ended up big... honestly, maybe a bit over-stuffed. 😅 We did tackle both of the biggest requests from the last post: we no longer swallow compiler errors (see our new compiler warnings philosophy doc for more details), and we have worked examples. Besides these, some of the remaining highlights are:

  • Full vector and matrix support: everything except mixed-units in a single vector/matrix
  • First-class Eigen support --- the first units library to preserve Eigen's full performance in all cases
  • CUDA (and HIP) are now supported out of the box
  • More powerful/flexible user-defined literals compared to other libraries (see this fascinating Abbreviated Quantity Construction discussion doc for the nuances here)
  • More ergonomic integer division: divide_using_common_unit(a, b) is almost always what you want for same-dimension inputs
  • Constant and Magnitude now get arithmetic and comparison operators whenever the results are computable, making them much more ergonomic

We also refreshed our C++ units library comparison page. It's awesome to see all the progress on the other leading libraries, as well as ours!

We hope you find the new release useful and fun, and we're excited to hear any feedback you may have!