Chandlerc

Chandler's blog about programming, languages, compilers, performance, cpus, tech, and everything else.

We have a recording available of this early preview now!!Video: https://drive.google.com/file/d/1tQlzpnbWZfn2WtTFMoJgF93QteByBBwm/view?usp=sharingSlides: https://chandlerc.blog/slides/2026-memory-safety-deep-3/Transcript: https://docs.google.com/document/

Recently, several of my colleagues at Google shared the story of how we are retrofitting spatial safety onto our monolithic C++ codebase: https://security.googleblog.com/2024/11/retrofitting-spatial-safety-to-hundreds.html I wanted to have a bit of story-

Chandler's blog about programming, languages, compilers, performance, cpus, tech, and everything else.

Note: This is the second of two guest blog posts from Carbon's Google-Summer-of-Code contributors this year. Introduction I'm Manmeet Singh, and I took part in Google Summer of Code 2023, contributing to the Editor Integration for the Carbon Language. In

Note: This is the first of two guest blog posts from Carbon's Google-Summer-of-Code contributors this year. Carbon Explorer is a prototype interpreter for Carbon whose primary purpose is to act as a clear executable specification of the language. It can a

Earlier this year, while at CppNow , I completely broke the RSS feed for this blog. Really sorry about that, and thanks to Jonathan for pointing it out. However, I have been distracted with work, life, and a bunch of complications over the intervening mon

This post is part of a series looking at little details of programming language design, mostly in the context of Carbon. Check out the series intro post for context and other entries. Let's talk about public vs. private ! Folks who know C++ may be familia

Working on a programming language is one of the most challenging and open ended design spaces that I have ever tried to operate in, both for existing and brand new languages. There are very few bounds or constraints on the solution space to help guide and