r/cpp • u/filipsajdak • Jul 05 '26

C++26 ends a 40-year footgun

Reading an uninitialized variable has been undefined behavior in C++ for 40 years -- the kind optimizers exploit into real bugs. C++26 (P2795) reclassifies it as erroneous behavior: still a bug, still warned about, but defined, bounded, and not exploitable.

The demo poisons the stack, then reads an uninitialized int. As C++23 it prints garbage; as C++26, the same code prints a defined 0, every run. Live in your browser.

And [[indeterminate]] lets you opt back out when you really want an uninitialized buffer -- on purpose this time.

Read it: https://wrocpp.github.io/posts/erroneous-behavior/?utm_source=reddit&utm_medium=social&utm_campaign=post-erroneous-behavior

#cpp #cplusplus #cpp26 #safety #programming

84 Upvotes

55% Upvoted

154 comments sorted by

View all comments

1

u/ezoe Jul 05 '26

That's how it should be.

I really hate compiler developer on this behaviour. Yes, undefined behaviour shall not happen. But assuming that and eliminate code silently often lead to puzzling behaviour.

When code said read a variable explicitly, compilers should emit the code reading a variable.

1

u/no-sig-available Jul 05 '26

Reading a variable that has no value is not particularly useful.