Merge pull request MicrosoftDocs#2392 from JordanMaples/patch-17

Colin Robertson · web-flow · commit 2aa7f40d5e5d · 2020-08-21T04:52:04.000-07:00
Add C++ Core Guidelines link to C26429
diff --git a/docs/code-quality/c26429.md b/docs/code-quality/c26429.md
@@ -12,7 +12,7 @@ ms.assetid: 4e1c74d5-7307-436c-927b-f74ae863282c
 "Symbol is never tested for nullness, it can be marked as gsl::not_null."
 
 **C++ Core Guidelines**:
-F.23: Use a not_null\<T> to indicate that "null" is not a valid value
+[F.23](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#f23-use-a-not_nullt-to-indicate-that-null-is-not-a-valid-value): Use a not_null\<T> to indicate that "null" is not a valid value
 
 It is a common practice to use asserts to enforce assumptions about validity of pointer values. The problem with asserts is that they do not expose assumptions through the interface (e.g. in return types or parameters). Asserts are also harder to maintain and keep in sync with other code changes. The recommendation is to use gsl::not_null from the Guidelines Support Library as a marker of resources which should never have null value. The rule USE_NOTNULL helps to identify places that omit checks for nullness and hence can be updated to use gsl::not_null.
 
