<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:media="http://search.yahoo.com/mrss/"><channel><title><![CDATA[Standard C++ | Standardization]]></title><description><![CDATA[Standard C++ | Standardization]]></description><link>https://isocpp.org/blog/rss/category/standardization</link><image><url>https://isocpp.org/apple-touch-icon-57.png</url><title>Standard C++ | Standardization</title><link>https://isocpp.org/blog/rss/category/standardization</link></image><generator>https://rss.app</generator><lastBuildDate>Fri, 21 Aug 2026 12:19:15 GMT</lastBuildDate><atom:link href="https://rss.app/feeds/8xXoTAuI5rXW7IXi.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><item><title><![CDATA[Trip report: June 2026 ISO C++ standards meeting (Brno, Czechia) -- Herb Sutter]]></title><description><![CDATA[<div><p>
	Hot off the press from the latest ISO C++ meeting:</p>
<blockquote>
	<h3>
		<a href="https://herbsutter.com/2026/06/13/brno-trip-report/">Trip report: June 2026 ISO C++ standards meeting (Brno, Czechia)</a></h3>
	<p>
		by Herb Sutter</p>
</blockquote>
<p>
	From the article:</p>
<blockquote>
	<h3>
		<em>tl;dr</em>… A few highlights</h3>
	<ul>
		<li>
			<em>Adopted this week in draft C++29:</em> Complete catalog of all undefined behavior (UB) in C++. Contract pre/post support for virtual functions. Defaulting (=default) for postfix increment/decrement. Designated initializers for base classes. Python-style .lookup(key) for associative containers. And more…</li>
		<li>
			<em>Other significant progress:</em> Progress on various features targeting C++29, including systematically addressing UB and adding safety profiles for C++.</li>
		<li>
			<em>Next six months:</em> Telecon line-by-line review of a proposal to systematically address all undefined behavior in C++. Progress adding C++ memory safety subsetting profiles. Both aim for inclusion in C++29.</li>
	</ul>
</blockquote></div>]]></description><link>https://rss.app/articles/cb4e791f6f6d729c1a4757416fc6fb8419195f6e1d33bde68db0d748d3c93791ad0bb75529c59c3db3fd2839c24e4acd35c86ae1c014664dc864d830c182577fd7e73bb6f4f124f1a58328a038e02408cf365d065c41fee9adda7f50c89fbea7c8ced494005a9a1bd5</link><guid isPermaLink="false">1194b6ce8075dc8ef48dda84e6cd7a13</guid><dc:creator><![CDATA[Blog Staff]]></dc:creator><pubDate>Mon, 15 Jun 2026 08:09:37 GMT</pubDate></item><item><title><![CDATA[Results summary: 2026 Annual C++ Developer Survey "Lite"]]></title><description><![CDATA[<div><p>
	<strong>Thank you </strong>to everyone who reponded to <a href="https://isocpp.org/blog/2026/04/2026-annual-cpp-developer-survey-lite1">our 2026 annual global C++ developer survey</a>. As promised, here is a summary of the results, including one-page summaries of your answers to the free-form questions:</p>
<blockquote>
	<h3>
		<a href="https://isocpp.org/files/papers/CppDevSurvey-2026-summary.pdf">CppDevSurvey-2026-summary.pdf</a></h3>
</blockquote>
<p>
	A 145-page version of this report that also includes all individual write-in responses has now been forwarded to the C++ standards committee and C++ product vendors, to help inform C++ evolution and tooling.</p>
<p>
	Your feedback is valuable, and appreciated.</p></div>]]></description><link>https://rss.app/articles/cb4e791f6f6d729c1a4757416fc6fb8419195f6e1d33bde68db0d748d3c93792ad4df50e6fc59d2db1e43f34c2574ace3d842aa8</link><guid isPermaLink="false">b2cc5ef22eea048edf546a63068f47c0</guid><dc:creator><![CDATA[Blog Staff]]></dc:creator><pubDate>Mon, 04 May 2026 21:04:35 GMT</pubDate></item><item><title><![CDATA[GCC 16.1 released: C++26 reflection / contracts / safety hardening, C++20 by default, and more!]]></title><description><![CDATA[<div><p>
	GCC 16.1 has been released! Lots of good C++26 material including reflection and contracts.</p>
<blockquote>
	<h3>
		<a href="https://gcc.gnu.org/gcc-16/changes.html#cxx">GCC 16 Release Series: Changes, New Features, and Fixes</a></h3>
</blockquote>
<p>
	From the announcement:</p>
<blockquote>
	<ul>
		<li>
			C++20 by default: [...] <em>N.B. C++20 modules support is still experimental and must be enabled by <a href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/C_002b_002b-Dialect-Options.html#index-fmodules">-fmodules</a>.</em></li>
	</ul>
	<ul>
		<li>
			Several C++26 features have been implemented:
			<ul>
				<li>
					<a href="https://wg21.link/P2996R13">P2996R13</a>, Reflection (<a href="https://gcc.gnu.org/PR120775">PR120775</a>, enabled by <code>-std=c++26 -freflection</code>)</li>
				<li>
					<a href="https://wg21.link/P3394R4">P3394R4</a>, Annotations for Reflection</li>
				<li>
					<a href="https://wg21.link/P3293R3">P3293R3</a>, Splicing a base class subobject</li>
				<li>
					<a href="https://wg21.link/P3096R12">P3096R12</a>, Function Parameter Reflection</li>
				<li>
					<a href="https://wg21.link/P3491R3">P3491R3</a>, <code>define_static_</code>{<code>string</code>,<code>object</code>,<code>array</code>} (<a href="https://gcc.gnu.org/PR120783">PR120783</a>)</li>
				<li>
					<a href="https://wg21.link/P3560R2">P3560R2</a>, Error Handling in Reflection</li>
				<li>
					<a href="https://wg21.link/P1306R5">P1306R5</a>, Expansion statements (<a href="https://gcc.gnu.org/PR120776">PR120776</a>)</li>
				<li>
					<a href="https://wg21.link/P2900R14">P2900R14</a>, Contracts (<a href="https://gcc.gnu.org/PR119061">PR119061</a>)</li>
				<li>
					<a href="https://wg21.link/P2795R5">P2795R5</a>, Erroneous behavior for uninitialized reads (<a href="https://gcc.gnu.org/PR114457">PR114457</a>)</li>
				<li>
					[...]</li>
			</ul>
		</li>
	</ul>
	<ul>
		<li>
			Improved experimental C++20 modules support:
			<ul>
				<li>
					New command line option <code>--compile-std-module</code> that conveniently builds the <code><bits/stdc++.h></code> header unit and the <code>std</code> and <code>std.compat</code> modules before compiling any source files explicitly specified on the command line.</li>
				<li>
					Whenever the <code><bits/stdc++.h></code> header unit has been built, GCC now transparently translates an <code>#include</code> of any importable standard library header into an <code>import</code> of <code><bits/stdc++.h></code>.</li>
				<li>
					Many reported bugs have been fixed, thanks to Nathaniel Shead.</li>
				<li>
					[...]</li>
			</ul>
		</li>
	</ul>
	<h4 id="libstdcxx">
		<a href="https://gcc.gnu.org/gcc-16/changes.html#libstdcxx">Runtime Library (libstdc++)</a></h4>
	<ul>
		<li>
			<code><font face="Consolas, Courier New, Lucida Console, monospace">[...]</font></code></li>
		<li>
			<code><font face="Consolas, Courier New, Lucida Console, monospace">Improved experimental support for [...]</font></code>
			<ul>
				<li>
					<code>std::mdspan</code>, thanks to Luc Grosheintz.</li>
				<li>
					<code>[...]</code></li>
				<li>
					<code>std::simd</code>.</li>
				<li>
					<code>std::inplace_vector</code>.</li>
				<li>
					<code>[...]</code></li>
			</ul>
		</li>
	</ul>
</blockquote></div>]]></description><link>https://rss.app/articles/cb4e791f6f6d729c1a4757416fc6fb8419195f6e1d33bde68db0d748d3c93793ad18a65f74d9d876f2</link><guid isPermaLink="false">0daa467207d71d8d5724e175623766ff</guid><dc:creator><![CDATA[Blog Staff]]></dc:creator><pubDate>Thu, 30 Apr 2026 22:36:23 GMT</pubDate></item><item><title><![CDATA[2026 Annual C++ Developer Survey "Lite"]]></title><description><![CDATA[<div><img src="https://isocpp.org/files/img/cpp_logo.png" style="width: 100%;" /><div><p>
	<img alt="cpp_logo.png" src="https://isocpp.org/files/img/cpp_logo.png" style="width: 250px; margin: 10px; float: right; height: 281px;max-width: 100%;" /></p>
<p>
	The annual global C++ developer survey is now open:</p>
<blockquote>
	<h2>
		<a href="https://standardcpp.typeform.com/2026-dev-survey">2026 Annual C++ Developer Survey "Lite"</a></h2>
</blockquote>
<p>
	Please share your feedback in this annual <strong>10-minute</strong> survey to help inform C++ standardization and C++ tool vendors. This is the biggest opportunity we all have each year to make our voices heard and help improve our industry and community!</p>
<p>
	A summary of the results, including aggregated highlights of common answers in the write-in responses, will be posted publicly here on isocpp.org and shared with the C++ standardization committee participants and C++ tool vendors to help inform C++ evolution and tooling.</p>
<p>
	The survey closes in one week.</p>
<p>
	<em><strong>Thank you </strong></em>for participating and helping to inform our committee and community.</p></div></div>]]></description><link>https://rss.app/articles/cb4e791f6f6d729c1a4757416fc6fb8419195f6e1d33bde68db0d748d3c93793ad4df50e6fc58f36ade73b21c2474fd37d813da7974e2454de79d820c4800c69daab39bbe1e671</link><guid isPermaLink="false">12ca1ad4a94d86ecbc6faa67fdbc1e18</guid><dc:creator><![CDATA[Blog Staff]]></dc:creator><pubDate>Wed, 22 Apr 2026 00:59:01 GMT</pubDate><media:content medium="image" url="https://isocpp.org/files/img/cpp_logo.png"/></item><item><title><![CDATA[CppCon 2025 How C++ Finally Beats Rust at JSON Serialization -- Lemire & Thiesen]]></title><description><![CDATA[<div><img src="https://isocpp.org/files/img/beatsrust-lemire.png" style="width: 100%;" /><div><p>
	<img alt="beatsrust-lemire.png" src="https://isocpp.org/files/img/beatsrust-lemire.png" style="width: 400px; margin: 10px; float: right;max-width: 100%;" />Registration is now open for CppCon 2026! The conference starts on September 12 and will be held <a href="https://cppcon.org/">in person in Aurora, CO</a>. To whet your appetite for this year’s conference, we’re posting videos of some of the top-rated talks from last year's conference. Here’s another CppCon talk video we hope you will enjoy – and why not <a href="https://cppcon.org/registration/"><strong>register today</strong></a><strong> for CppCon 2026!</strong></p>
<blockquote>
	<h3>
		<a href="https://www.youtube.com/watch?v=Mcgk3CxHYMs">How C++ Finally Beats Rust at JSON Serialization</a></h3>
	<p>
		by Daniel Lemire & Francisco Geiman Thiesen</p>
</blockquote>
<p>
	Summary of the talk:</p>
<blockquote>
	<p>
		JSON, or JavaScript Object Notation, has become a cornerstone for storing and exchanging data. Its appeal lies in its simplicity—human-readable text that elegantly captures structured data through attribute-value pairs and arrays: {"age": 5, "name": "Daniel", "toys": ["wooden dog", "little car"]}. JSON is intuitive yet powerful. But ingesting and producing JSON can turn into a performance choke point. In C++, it can be a tedious, error-prone task. Programmers wrestle with unexpected content, manually mapping data to and from native structures, all while striving for speed and safety.<br />
		<br />
		With languages like Java, C#, Zig, Rust, or Python, JSON serialization and deserialization typically requires far less work. In particular, Rust's serde library blends convenience with high speed. We wish for a C++ library to automatically handle JSON production and consumption, seamlessly tied to native data structures. It is not merely to simplify life for developers; it is also about crafting code that is both fast and solid, generated at compile time by a battle-tested library.<br />
		<br />
		Thankfully, C++ might soon be getting reflective metaprogramming (  PR2996  ). Leveraging the  experimental Bloomberg LLVM fork  with reflective metaprogramming, we have built a full-fledged implementation—complete with tests, benchmarks, and documentation. Our goal is to have production-ready code the moment mainstream compilers catch up. The results speak for themselves: we are parsing JSON directly into C++ structures at gigabytes per second, outpacing even mature heavyweights like Rust's serde. Better yet, the conversion between C++ data structures and JSON is fully automated, thanks to metaprogramming. It has the potential to be a leap forward for C++ in the data-driven age. Unfortunately, there are still problems and limitations: we present them and provide some solutions.</p>
</blockquote></div></div>]]></description><link>https://rss.app/articles/cb4e791f6f6d729c1a4757416fc6fb8419195f6e1d33bde68db0d748d3c93793ad1cb54c3a878075f1a26878c24c50d47d8628a1df44224ada67992a9c901f6dd7f578a0e0f034afe99a60af3fe6244291315d015200f4e9a9cd7e56c79fbaa7d7c58b82585a8617c2806f6b</link><guid isPermaLink="false">e1262a3f7d4188f89b8766e16ae92d0a</guid><dc:creator><![CDATA[Blog Staff]]></dc:creator><pubDate>Fri, 17 Apr 2026 19:34:43 GMT</pubDate><media:content medium="image" url="https://isocpp.org/files/img/beatsrust-lemire.png"/></item></channel></rss>