Docs: missing guidance on null guards

[bitbonk]

There has been some discussion and misunderstanding on whether or not application and/or library developers now can remove any null guards (e.g. if(input != null){...}, ArgumentNullException) because of this feature. See for example here and here. The documentation needs clear guidance if or if not (and if so, when) it is now safe to remove null guards.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: bea1e2ab-5517-b17c-4a65-7c7bae09261a
• Version Independent ID: 2a326631-709b-4461-6c15-a75a5087ef1d
• Content: Nullable reference types in C# - C# 8.0 language proposals
• Content Source: proposals/csharp-8.0/nullable-reference-types.md
• Product: dotnet-csharp
• Technology: csharp-spec
• GitHub Login: @dotnet-bot
• Microsoft Alias: wiwagn

[BillWagner]

Thanks for writing this @bitbonk

The reference guidance for corefx is a good start. However, as we add more annotations to different APIs in corefx, we're continuing to learn the best way forward. We're not comfortable saying "we know the answers" yet.

I've not assigned this a milestone, because we're not confident enough of the current guidance to recommend it universally. However, I've adding a high priority label because we agree it's important.

[bitbonk]

@IEvangelist Can you clarify why this was closed? Where can I see the updated docs for this?

[BillWagner]

@bitbonk The PR was merged today. It will be published overnight, on our regular publishing cycle.

If you can't wait, the source is here on GitHub.

[IEvangelist]

Sorry, @bitbonk -- I should have commented with an explanation. I'll be sure to make that a part of my standard workflow from now on. Thanks for keeping me honest 👍