Large C++ projects often spend a surprising amount of time repeatedly parsing the same third-party headers. Header-only and template-heavy libraries make this even worse: every translation unit pays the cost again.

C++20 Modules provide a way out, but fully migrating a large codebase from #include to import is rarely realistic. This article describes a more incremental approach: use Clang module maps to translate selected #include directives into module imports during the build, while keeping application source code unchanged.

I built a header-only proto3 wire-format library with one constraint: no .proto files, no codegen, no descriptor runtime. The user writes a plain C++ struct, and that struct is the schema:

Overview

This is a late summary of 2025—the calendar has turned to February 2026.

In the past year, almost all of my time was devoted to the Bazel build system: a unified build system based on Bazel for projects in all languages. I had originally planned to spend time on Triton, but ended up with none. The LLVM JIT effort was suspended due to business changes, and no effort went into ClangIR.