Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    Very good point. Recent version of C# use ? and ! constructs to handle nullability, and catch possible null error at compile time. Commented May 9, 2023 at 17:21
  • Exactly, @JotaBe! And if the compiler mandated them, then you would never be surprised by a null-based error again 🖤 Commented May 15, 2023 at 17:37
  • Yes, forcing it it's something you can configure at the project level. This allows to migrate old projects to newer C# versions, and "procrastinate" updating them to correctly handle the nulls at compile time. When you enable it, the static analysis allows you to find all the possible null related problems. Commented Jun 14, 2023 at 9:57