Trip Report: Spring ISO C++ Meeting in Tokyo, Japan -- Jonathan Müller
Last week, I attended the spring 2024 meeting of the ISO C++ standardization committee in Tokyo, Japan. This was the third meeting for the upcoming C++26 standard and my first meeting as assistant chair of SG 9, the study group for ranges.
Trip Report: Spring ISO C++ Meeting in Tokyo, Japan
by Jonathan Müller
From the article:
I started the week on Monday in LEWG, the working group for the C++ standard library design. After the usual papers adding/extending
std::format(Victor Zverovich keeps us busy), we approved a proposal that adds thread attributes, and reviewed the library parts of P2900 contracts. LEWG being LEWG, we mostly complained about the names (std::contracts::contract_violationhas too many contracts in it), but overall liked it. However, contracts are a language feature, and the real controversy was over at EWG, the language design group. In particular, what happens if you have undefined behavior in a precondition? Consider the following example:std::string_view slice(std::string_view str, int pos, int length) pre (0 <= pos && pos <= std::ssize(str) && 0 <= length && pos + length <= std::ssize(str)) { return std::string_view(str.data() + pos, str.data() + pos + length); }A slicing function for std::string_view using signed integers for demonstration purposes.
An integer overflow of
pos + lengthin the precondition is undefined behavior. Some argue that this should instead be well-defined and lead to a precondition violation. While this would be nice and can lead to a general "safe mode" of C++ which could (and should!) be usable outside of contracts as well, I don't see how it can be worked out before C++26. I'd much rather have contracts with undefined behavior in C++26 then delaying it even further. The nice thing about undefined behavior is that it can be always well-specified later.
A new episode of the series about SObjectizer and message passing:
A new episode of the series about SObjectizer and message passing:
I delivered a keynote, C++ and the Next 30 Years, at the 2024 CPP-Summit conference in Beijing, China. Experiencing the culture, the people, and the landscape was tremendous. In this post I’ll cover some of the points in my future-looking C++ talk and share my experience giving a talk for the first time in China.
In C++, shadowing occurs when a name in one scope hides an identical name in another scope, sparking debate over its merit. This article explores scenarios where shadowing can either protect code integrity or hinder its evolution, highlighting its dual nature and impact on code maintenance. Join Raymond as he unravels the complexities of shadowing in C++, revealing its intricate balance between benefit and drawback.
A new episode of the series about SObjectizer and message passing:
In this post, we continue discovering the changes introduced by C++23. We are going to look into three (and a half) small changes, each affecting constructors of some standard library types. We’re going to see how new constructors for container types, a new range constructor for 
Last year saw a proliferation of talks and articles about safety in C++. Lucian Radu Teodorescu gives an overview of these and presents a unified perspective on safety.