Nullability in C# 8.0
summary
C# 8 adds nullable reference types as annotations so existing nonnullable types become the default, using the ? operator and a lexical nullable enable directive that can be applied per file. The compiler emits warnings (Roslyn saw ~3,500–4,000 initially) and uses flow analysis plus new attributes (DoesNotReturn, NotNullWhen, etc.) to learn common patterns. Incremental adoption strategies and SDK annotations reduce churn; the feature ships and finds real bugs while keeping runtime behavior unchanged.
AI-written summary · about
chapters (18)
- 0:00Start
- 0:16Jared Parsons
- 1:25BILLION DOLLAR MISTAKE
- 2:03C# AND NULL REFERENCES
- 2:48CREATING VS. EXTENDING
- 6:23WHAT ABOUT AN API SOLUTION?
- 7:50COMPONENTS FOR SUCCESS
- 9:10LOTS OF C# CODE TO ANNOTATE
- 10:17CANT ENABLE IN ONE CHANGE
- 12:22NET HAS A BROAD ECOSYSTEM
- 14:29PRINCIPLES
- 41:11REVIEW
- 41:47NET CORE 3.0
- 42:51NET AND NULLABILITY GOING FORWARD
- 43:57RECOMMENDATION FOR LIBRARY AUTHORS
- 44:43ADOPTION STRATEGIES
- 47:16ADOPTION EXAMPLES
- 47:27MORE RESOURCES (2)
related talks
01h 01mC# 8
57m'nullable' enable – Unlock the Power of C# Nullability
13mWhat's New in C# 8.0
01h 06mNull & Void - Everything about Nothing in .NET
01h 00mWhat's new in C#? Exciting new features in C# 8.0, 9.0 and 10!
43mWhat’s coming in C# 8.0?
01h 13mNull & Void – Everything About Nothing in .NET
59mWhat's new in C#? Exciting new features in C# 8.0, 9.0 and 10!
