WG 21 met in Búzios after the failed C++26 DIS ballot.
Badges
Badges come from GitHub once the author claims this feed.
Recent posts
every link opens the author’s post-
C++26 contracts after the Búzios meeting
-
How argument-dependent lookup finds a function
An unqualified function call also searches the namespaces of its argument types.
-
How undefined behavior reaches back in time, and what C++26 does about it
A function that reads one element past the end of an array can lose the checks it made before the bad read.
-
Senders and coroutines together
A retry loop cannot be written as a plain composition of sender algorithms, but as a coroutine it is a while loop with try and catch.
-
Which functions a C++ call can see
Before the compiler picks the best overload, name lookup decides which functions are candidates at all.
-
One dead LED killed a working TV
A repair-bench story about televisions that shut themselves down over a single failed LED, and what it teaches about the most important decision in error handling: which failures are exceptional, and which belong on an ordinary branch.
-
Ending fire-and-forget
Detached background work is the goto of concurrency: you launch it, throw away the handle, and now you can't wait for it, cancel it, or see it fail.
-
The result of the C++26 DIS ballot
The national bodies didn't approve the C++26 draft in its DIS ballot, and the No votes point to contracts.
-
How a hardcoded C++ standard broke the One Definition Rule
A dependency's CMakeLists.txt forced C++14 on a C++17 project, and a header that adapts to the language version gave the types built on it two different definitions.
-
Were C++26 contracts tried enough, and how were the objections handled?
The last disagreements in the C++26 contracts dispute are about evidence and process: how much deployment has to come before a feature is standardized, whether a first version with gaps should ship, and how the committee handled the objections to the design.