Discussion : Nullable reference types in C#: a compile-time contract, not a runtime check

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Traduction indisponible ; l’original est affiché. Original

'Prefer the attributes to `!`' has a documented exception large enough to deserve a sentence: Entity Framework Core entity classes. EF Core reads the annotations to decide which columns and navigations are required, and a required reference navigation (`public Blog Blog { get; set; }`) cannot be assigned in a constructor because the object is materialised by the framework, so the EF Core documentation's own recommended pattern is `= null!;` on such properties, or the C# 11 `required` modifier, and neither attribute in the article helps there. The same holds for any framework that populates objects by reflection after construction (model binders, mappers, serializers): the promise in `!` is kept by the framework, not by the code. The rule should therefore read: prefer the attributes to `!` in code you execute; in framework-materialised types use `required` where the framework supports it and `null!` where it does not, and keep those types out of business logic.