Frank R. Haugen Public work / dev log

If you can watch it compile, you might actually learn

compilers education RoboSharp

Most beginner stacks are designed to hide the pipeline: lexer, parser, binder, IL, runtime — all of that is “magic happens here” with a cartoon mascot and a green checkmark.

RoboSharp is the opposite on purpose. The point is not the robot on the grid; the robot is the excuse. The point is that you can see the stages update while you edit: tokens, syntax, bound tree, IL, interpreter. Boring, finicky, real computer science — the stuff textbooks skip because it does not fit on a slide.

Facts: what a compiler pipeline usually contains

Textbooks divide compilation into predictable phases—names vary, but the skeleton is stable:

Phase Removes ambiguity…
Lexical analysis Characters → tokens (if, identifiers, literals).1
Syntax analysis Tokens → parse tree / AST respecting grammar.2
Semantic analysis Types, scopes, overload resolution — whether the AST means something legal.3
Intermediate representation Portable IR before CPU-specific codegen (LLVM bitcode, .NET IL, etc.).
Optimization + codegen Maps IR → machine code or VM bytecode.

Engineering a Compiler (Cooper & Torczon) presents the same pipeline with engineering emphasis—trade-offs between IR shapes, passes, and diagnostics quality.4

For .NET, Roslyn exposes compiler APIs so tooling (IDE refactorings, analyzers, source generators) shares the same frontend as csc. Microsoft’s conceptual docs describe syntax trees, semantic models, and workspaces for building analyzers.5

Why visibility beats “just use the API”

When the API is the curriculum, you learn one vendor’s opinion. When the pipeline is the curriculum, you learn how languages actually work, which transfers even when the framework du jour changes its mind next Tuesday.

The honest downside

It is more intimidating. Some people bounce off immediately because there is no dopamine tutorial path where you “build Instagram in ten minutes.” Good. Instagram already exists. I would rather have a smaller audience that sticks around because the machine finally clicked.

TL;DR

If you can watch it compile, you might hate it for an hour — then you might never unsee how much software you use every day was always doing this work under the hood.

References

  1. Aho, Lam, Sethi, Ullman — Compilers: Principles, Techniques, and Tools (2nd ed., 2006), lexical analysis chapter overview. ISBN 978-0321486813 — publisher Pearson. ↩

  2. Same — syntax analysis / parsing theory sections. ↩

  3. Same — semantic analysis / type checking introduction. ↩

  4. Cooper & Torczon — Engineering a Compiler (2nd ed., Morgan Kaufmann). https://www.elsevier.com/books/engineering-a-compiler/cooper/978-0120884780 ↩

  5. Microsoft Learn — The .NET Compiler Platform SDK (Roslyn APIs) overview. https://learn.microsoft.com/dotnet/csharp/roslyn-sdk/ ↩