GoKawiil“Hardening” seems to be a very popular term in the C++ World in 2026. In this article we’ll explore what this word means and see some core examples. Can a hardened library make C++ fully safe? Let’s find out.
The Core Idea
When you learned about std::vector you may remember that you can access an element at the i -th position using at least two expressions:
std :: vector < int > v { 1 , 2 , 3 , 4 }; v [ i ] = 10 ; // for some i v . at ( j ) = 11 ; // for some j
The main difference between those two is that [] is unchecked (and can generate undefined behaviour if you try to access an element which is not there), while .at() may throw std::out_of_range (so it’s a well defined behaviour).
C++26 Changes
In C++26, the Standard introduces the notion of a hardened implementation. Whether a standard-library implementation is hardened, and how that mode is enabled, is implementation-defined.
For std::vector<T, Allocator>::operator[](size_type pos) :
C++ Standard Condition until C++26 If pos < size() is false , the behavior is undefined. since C++26 If pos < size() is false : If the implementation is hardened, a contract violation occurs, If the implementation is not hardened, the behavior is undefined.
In other words, if you switch this “hardened” mode you’ll get some well specified error/violation rather than just an undefined behaviour.
... continue reading