Skip to main content

.NET 9 upgrade–notnull constraint

With the Christmas Holidays after us, I finally got some time to start upgrading some older .NET Core applications to .NET 9. First thing I noticed after upgrading is that I got some new warnings related to the ‘notnull’ constraint.

The ‘notnull’ constraint was introduced as part of the nullable reference types feature in C#.  The goal of nullable reference types was to solve the ‘million dollar mistake’ and help you to prevent common issue of null reference exceptions. They allow  to explicitly state whether a reference type variable can be null or not, helping to catch potential null dereferences at compile time.

The feature is in fact a combination of multiple elements all with the goal of avoiding unexpected null reference exceptions:

  • Nullable and Non-Nullable Reference Types:

    • Non-Nullable: If you declare a reference type without the ? suffix (e.g., string name), it is considered non-nullable. The compiler issues warnings if you try to assign a null value to it.

    • Nullable: If you declare a reference type with the ? suffix (e.g., string? name), it can hold a null value. The compiler warns you when you might dereference it without a null check.

  • Null-State Analysis: The compiler tracks the null-state of each variable, which can be either not-null or maybe-null. It issues warnings if there's a possibility of a null dereference.

  • Annotations and Attributes: You can use various attributes (like [NotNullWhen(false)]) and annotations to give the compiler more information about the nullability of parameters and return values in methods.

    • As part of this feature a new generic constraint was introduced, the ‘notnull’ constraint. This guarantees that the provided type is a non-nullable type. This can either be a non-nullable reference type or a non-nullable value type.

    Remark: As this feature was introduced already in C# 8.0, I think it is just a coincidence I noticed it only after upgrading to .NET 9. One extra reason to enable the ‘Treat warnings as errors’ flag…

    I got 2 places where I got this warning:

    ModuleExtensions.cs(83,137,83,144): warning CS8714: The type 'T' cannot be used as type parameter 'TKey' in the generic type or method 'Dictionary<TKey, TValue>'. Nullability of type argument 'T' doesn't match 'notnull' constraint.

    NoOpLogger.cs(15,24,15,34): warning CS8633: Nullability in constraints for type parameter 'TState' of method 'NoOpLogger.BeginScope<TState>(TState)' doesn't match the constraints for type parameter 'TState' of interface method 'ILogger.BeginScope<TState>(TState)'. Consider using an explicit interface implementation instead.

    Here is each time the original code and the fix:

    Original code:

    Fix:

    Original code:

    Fix:

    More information

    Nullable reference types - C# | Microsoft Learn

    The history of C# | Microsoft Learn

    Labels:

    Popular posts from this blog

    Podman– Command execution failed with exit code 125

    After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
    Read more

    Cache stampede: when our cache turned against us

    While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
    Read more

    A complex system designed from scratch never works

    A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
    Read more