What are the key takeaways from this Software Engineering Daily episode?

Key insights include: **C++ Interop Architecture:** Carbon uses Clang to parse C++ into AST, synthesizes bidirectional representations between Carbon's semantic IR and C++'s AST, then merges both into LLVM IR. This enables zero-copy data passing and supports complex features like virtual inheritance across language boundaries without runtime overhead.; **Parameter Passing Optimization:** C++ forces developers to choose between pass-by-value and const-reference for every function parameter based on type size, creating decision overhead and performance penalties. Carbon provides one unified input parameter syntax that automatically optimizes for each type, eliminating pointer indirection for small types like integers.; **Definition-Checked Generics:** Carbon implements checked generic programming that validates code at definition time rather than instantiation, enabling memory safety features similar to Rust while maintaining template compatibility for C++ interop. This reduces code duplication and compile-time costs compared to C++ template instantiation for every type combination.

What did Chandler Carruth discuss on Software Engineering Daily?

Chandler Carruth explains Carbon, Google's experimental successor to C++, designed to provide memory safety and modern features while maintaining seamless interoperability with existing C++ codebases through advanced compiler technology and bidirectional AST translation. Key topics include: **C++ Interop Architecture:** Carbon uses Clang to parse C++ into AST, synthesizes bidirectional representations between Carbon's semantic IR and C++'s AST, then merges both into LLVM IR. This enables zero-copy data passing and supports complex features like virtual inheritance across language boundaries without runtime overhead.; **Parameter Passing Optimization:** C++ forces developers to choose between pass-by-value and const-reference for every function parameter based on type size, creating decision overhead and performance penalties. Carbon provides one unified input parameter syntax that automatically optimizes for each type, eliminating pointer indirection for small types like integers..

How long is this episode of Software Engineering Daily?

This episode is 62 minutes long. SignalCast provides an AI-generated summary so you can get the key insights in about 3 minutes.

Software Engineering Daily

Carbon and Modernizing C++ with Chandler Carruth

August 14, 2025

62 min episode · 2 min read

Chandler Carruth

Episode

62 min

Read time

2 min

Topics

Design & UX, Software Development, Product & Tech Trends

AI-Generated Summary

Published Dec 25, 2025

Key Takeaways

✓C++ Interop Architecture: Carbon uses Clang to parse C++ into AST, synthesizes bidirectional representations between Carbon's semantic IR and C++'s AST, then merges both into LLVM IR. This enables zero-copy data passing and supports complex features like virtual inheritance across language boundaries without runtime overhead.
✓Parameter Passing Optimization: C++ forces developers to choose between pass-by-value and const-reference for every function parameter based on type size, creating decision overhead and performance penalties. Carbon provides one unified input parameter syntax that automatically optimizes for each type, eliminating pointer indirection for small types like integers.
✓Definition-Checked Generics: Carbon implements checked generic programming that validates code at definition time rather than instantiation, enabling memory safety features similar to Rust while maintaining template compatibility for C++ interop. This reduces code duplication and compile-time costs compared to C++ template instantiation for every type combination.
✓Incremental Migration Path: Developers can automatically translate C++ code to Carbon syntax, then incrementally add constraints to templates without breaking existing code. Once constraints propagate through dependencies, templates convert to checked generics, delivering better error messages and reduced binary size while maintaining full functionality throughout migration.
✓Governance Through Painter Role: Carbon's three-lead structure includes a painter who breaks aesthetic ties only when no technical rationale exists. This mechanism forces contributors to articulate technical reasons for preferences rather than arguing aesthetics, resulting in almost zero purely aesthetic decisions while maintaining rapid decision velocity.

What It Covers

Chandler Carruth explains Carbon, Google's experimental successor to C++, designed to provide memory safety and modern features while maintaining seamless interoperability with existing C++ codebases through advanced compiler technology and bidirectional AST translation.

Key Questions Answered

•C++ Interop Architecture: Carbon uses Clang to parse C++ into AST, synthesizes bidirectional representations between Carbon's semantic IR and C++'s AST, then merges both into LLVM IR. This enables zero-copy data passing and supports complex features like virtual inheritance across language boundaries without runtime overhead.
•Parameter Passing Optimization: C++ forces developers to choose between pass-by-value and const-reference for every function parameter based on type size, creating decision overhead and performance penalties. Carbon provides one unified input parameter syntax that automatically optimizes for each type, eliminating pointer indirection for small types like integers.
•Definition-Checked Generics: Carbon implements checked generic programming that validates code at definition time rather than instantiation, enabling memory safety features similar to Rust while maintaining template compatibility for C++ interop. This reduces code duplication and compile-time costs compared to C++ template instantiation for every type combination.
•Incremental Migration Path: Developers can automatically translate C++ code to Carbon syntax, then incrementally add constraints to templates without breaking existing code. Once constraints propagate through dependencies, templates convert to checked generics, delivering better error messages and reduced binary size while maintaining full functionality throughout migration.
•Governance Through Painter Role: Carbon's three-lead structure includes a painter who breaks aesthetic ties only when no technical rationale exists. This mechanism forces contributors to articulate technical reasons for preferences rather than arguing aesthetics, resulting in almost zero purely aesthetic decisions while maintaining rapid decision velocity.

Notable Moment

Carruth reveals that C++ compile times measured in minutes for text processing represent a fundamental failure compared to millisecond turnarounds in modern JavaScript tooling. Carbon targets interactive-speed compilation through novel semantic IR architecture that enables faster parsing and compile-time evaluation than traditional AST approaches.

Know someone who'd find this useful?

Episode Transcript

Carbon is a programming language developed by Google as a successor to c plus plus and it aims to provide modern safety features while maintaining high performance. It's designed to offer seamless interoperability with c plus plus while addressing shortcomings of c plus plus such as slow compilation times and lack of memory safety. Carbon also introduces features like a more readable syntax, improved generics, and automatic memory management while still allowing low level control. Chandler Carruth is the creator of Carbon, and he leads the c plus plus, CLANG, and LLVM teams at Google, and he also worked on several pieces of Google's distributed build system. In this episode, he joins Kevin Ball to talk about Carbon and the future of the language. Kevin Ball, or Kay Ball, is the vice president of engineering at Mento and an independent coach for engineers and engineering leaders. He cofounded and served as CTO for two companies, founded the San Diego JavaScript meetup, and organizes the AI in Action discussion group through Latent Space. Check out the show notes to follow Kay Ball on Twitter or LinkedIn, or visit his website, kball.llc. Chandler, welcome to the show. Really happy to be here. Really happy to be here. Yeah. I'm excited to dig in. So let's maybe start with a little bit about you, your background, and a little bit about what Carbon is and what led to it. Sure. Sure. I mean, I've been a software engineer at Google for a long time now. And when I started, I was pretty fresh out of university and didn't really know what I was doing kind of got thrown into a bit of the deep end. And I was working on a c plus plus project with a bunch of amazing folks who are largely teaching me how to be a good software engineer. And I was incredibly frustrated because the C plus plus project was just holding me back every single step of the way working on the C plus plus code base was painful. The tools were bad. The experience was bad. And it seemed like it really it just it became an overwhelming kind of problem that we needed to solve. And that kind of kick started me diving a whole lot deeper into first compilers because I thought maybe the compiler was the problem. And as we got better and better compilers, then enter the programming language, joined the standards committee, really tried to figure out ways we could much more radically improve c plus plus the experience for all the developers, and also the quality of the actual software we're able to put out. At a certain point, we weren't actually able to achieve the kind of improvements we needed to. We kept seeing really fundamental risks facing c plus plus really fundamental problems that needed pretty radical changes to the programming language as a whole and that the kind of how the programming language worked in order to …

Get the full transcript (12,344 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all Software Engineering Daily transcripts →