Nullable Reference Types

A C# compiler feature (introduced in C# 8.0) that helps prevent null reference exceptions: the billion-dollar mistake that Tony Hoare apologized for in 2009 and that has haunted every C# developer since the language was invented. When enabled, the compiler distinguishes between types that can be null (string?) and types that should never be null (string), and warns you when you're about to do something that will blow up at 2 AM on a Friday.

Why it matters for writers: This isn't just a niche language feature. It represents the kind of modern C# improvement that makes the language genuinely pleasant for AI development. Pattern matching, nullable reference types, records, file-scoped namespaces; these aren't just syntax sugar. They produce code that's easier to read, document, and maintain. When blog posts mention C# having "nullable reference types and pattern matching," they're gesturing at a broader argument: C# is a legitimate choice for AI tooling despite the ecosystem's Python bias, and the language itself is part of the reason.

Related terms: Pattern Matching · Records · File-Scoped Namespaces