Merge pull request MicrosoftDocs#2433 from MicrosoftDocs/master637347533073753485

Repo sync for protected CLA branch

Author: Colin Robertson

docs/code-quality/c26462.md

@@ -4,7 +4,26 @@ ms.date: 03/22/2018
 ms.topic: reference
 f1_keywords: ["C26462"]
 helpviewer_keywords: ["C26462"]
+description: CppCoreCheck rule that enforces C++ Core Guidelines Con.4
 ---
 # C26462 USE_CONST_POINTER_FOR_VARIABLE
 
-The value pointed to by '%variable%' is assigned only once, mark it as a pointer to `const`. See [C++ Core Guidelines con.4](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#con4-use-const-to-define-objects-with-values-that-do-not-change-after-construction).
+The value pointed to by '%variable%' is assigned only once, mark it as a pointer to `const` (con.4). 
+
+Pointers to variables whose values remain unchanged should be marked as const.
+
+## See also
+[C++ Core Guidelines con.4](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#con4-use-const-to-define-objects-with-values-that-do-not-change-after-construction).
+
+## Example
+```cpp
+void useVal(int val);
+
+void function1(int* ptr)
+{
+    int* p = ptr; // C26462, the value pointed to by p is unmodified
+    ptr = nullptr;
+
+    useVal(*p);
+}
+```

docs/code-quality/c26463.md

@@ -4,7 +4,14 @@ ms.date: 03/22/2018
 ms.topic: reference
 f1_keywords: ["C26463"]
 helpviewer_keywords: ["C26463"]
+description: CppCoreCheck placeholder warning for future con.4 enforcement
 ---
 # C26463 USE_CONST_FOR_ELEMENTS
 
-The elements of array '%array%' are assigned only once, mark elements `const`. See [C++ Core Guidelines con.4](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#con4-use-const-to-define-objects-with-values-that-do-not-change-after-construction).
+The elements of array '%array%' are assigned only once, mark elements `const` (con.4)
+
+## See also
+[C++ Core Guidelines con.4](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#con4-use-const-to-define-objects-with-values-that-do-not-change-after-construction).
+
+## Remark
+- This rule is currently not implemented in CppCoreCheck. 

docs/code-quality/c26464.md

@@ -4,7 +4,14 @@ ms.date: 03/22/2018
 ms.topic: reference
 f1_keywords: ["C26464"]
 helpviewer_keywords: ["C26464"]
+description: CppCoreCheck placeholder warning for future con.4 enforcement
 ---
 # C26464 USE_CONST_POINTER_FOR_ELEMENTS
 
-The values pointed to by elements of array '%array%' are assigned only once, mark elements as pointer to `const`. See [C++ Core Guidelines con.4](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#con4-use-const-to-define-objects-with-values-that-do-not-change-after-construction).
+The values pointed to by elements of array '%array%' are assigned only once, mark elements as pointer to `const` (con.4). 
+
+## See also
+[C++ Core Guidelines con.4](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#con4-use-const-to-define-objects-with-values-that-do-not-change-after-construction).
+
+## Remarks
+- This rule is currently not implemented in CppCoreCheck. 

docs/code-quality/c26483.md

@@ -4,7 +4,24 @@ ms.date: 03/22/2018
 ms.topic: reference
 f1_keywords: ["C26483"]
 helpviewer_keywords: ["C26483"]
+description: CppCoreCheck rule that enforces C++ Core Guidelines Bounds.2
 ---
 # C26483 STATIC_INDEX_OUT_OF_RANGE
 
-Value %value% is outside the bounds (0, %bound%) of variable '%variable%'. Only index into arrays using constant expressions that are within bounds of the array. See [C++ Core Guidelines Bounds.2](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#SS-bounds)
+Value %value% is outside the bounds (0, %bound%) of variable '%variable%'. Only index into arrays using constant expressions that are within bounds of the array (bounds.2). 
+
+## See also
+[C++ Core Guidelines Bounds.2](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#SS-bounds)
+
+## Example
+```cpp
+void function()
+{
+    std::array<int, 3> arr1 { 1, 2, 3 };
+    arr1[3] = 4; // C26483, 3 is outside the bounds of the array
+    
+    int arr2[] { 1, 2, 3 };
+    arr2[3] = 4; // C26483, 3 is outside the bounds of the array
+}
+
+```

docs/code-quality/c26495.md

@@ -4,7 +4,29 @@ ms.date: 03/22/2018
 ms.topic: reference
 f1_keywords: ["C26495"]
 helpviewer_keywords: ["C26495"]
+description: CppCoreCheck rule that enforces C++ Core Guidelines Type.6
 ---
 # C26495 MEMBER_UNINIT
 
-Variable '%variable%' is uninitialized. Always initialize a member variable. See [C++ Core Guidelines Type.6](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#SS-type).
+Variable '%variable%' is uninitialized. Always initialize a member variable (type.6). 
+
+## See also
+C++ Core Guidelines [Type.6](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#SS-type) and [C.48](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#c48-prefer-in-class-initializers-to-member-initializers-in-constructors-for-constant-initializers)
+
+
+## Example
+```cpp
+struct MyStruct 
+{
+    int value;
+    MyStruct() {}; // C26495, MyStruct::value is uninitialized
+};
+```
+To fix the warning, add in-class initializers to all of the member variables. See the above linked C++ Core Guidelines pages for additional information.
+```cpp
+struct MyStruct 
+{
+    int value{};
+    MyStruct() {}; // no warning, MyStruct::value is set via default member initialization
+};
+```

docs/code-quality/c26496.md

@@ -4,7 +4,26 @@ ms.date: 03/22/2018
 ms.topic: reference
 f1_keywords: ["C26496"]
 helpviewer_keywords: ["C26496"]
+description: CppCoreCheck rule that enforces C++ Core Guidelines Con.4
 ---
 # C26496 USE_CONST_FOR_VARIABLE
 
-> The variable '*variable*' is assigned only once, mark it as `const`. See [C++ Core Guidelines con.4](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#con4-use-const-to-define-objects-with-values-that-do-not-change-after-construction).
+> The variable '*variable*' is assigned only once, mark it as `const`. 
+
+## See also
+[C++ Core Guidelines con.4](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#con4-use-const-to-define-objects-with-values-that-do-not-change-after-construction).
+
+## Example
+```cpp
+int GetTheNumber();
+int GiveMeTheNumber(int);
+
+void function1()
+{
+    int theNumber = GetTheNumber(); // C26496, 'theNumber' is never assigned to again, so it can be marked as const
+    std::cout << theNumber << '\n';
+    
+    GiveMeTheNumber(theNumber);
+    // ...
+}
+```

docs/code-quality/c26497.md

@@ -4,7 +4,21 @@ ms.date: 03/22/2018
 ms.topic: reference
 f1_keywords: ["C26497"]
 helpviewer_keywords: ["C26497"]
+description: CppCoreCheck rule that enforces C++ Core Guidelines F.4
 ---
 # C26497 USE_CONSTEXPR_FOR_FUNCTION
 
-This function %function% could be marked `constexpr` if compile-time evaluation is desired. See [C++ Core Guidelines F.4](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#Rf-constexpr).
+This function %function% could be marked `constexpr` if compile-time evaluation is desired (f.4).  
+
+## See also
+[C++ Core Guidelines F.4](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#Rf-constexpr).
+
+## Example
+```cpp
+const int GetTheAnswer(int x) noexcept { return 42 + x; } // Could be marked constexpr
+
+void function1() noexcept
+{
+    const int theAnswer = GetTheAnswer(0);
+}
+```

docs/parallel/amp/cpp-amp-cpp-accelerated-massive-parallelism.md

@@ -29,6 +29,6 @@ C++ AMP (C++ Accelerated Massive Parallelism) accelerates the execution of your
 
 ## Other Resources
 
-[Parallel Programming in Native Code Blog](https://go.microsoft.com/fwlink/p/?linkid=238472)<br/>
-[C++ AMP sample projects for download](https://go.microsoft.com/fwlink/p/?linkid=248508)<br/>
+[Parallel Programming in Native Code Blog](/archive/blogs/nativeconcurrency/)<br/>
+[C++ AMP sample projects for download](/archive/blogs/nativeconcurrency/c-amp-sample-projects-for-download)<br/>
 [Analyzing C++ AMP Code with the Concurrency Visualizer](/archive/blogs/nativeconcurrency/analyzing-c-amp-code-with-the-concurrency-visualizer)

docs/parallel/amp/cpp-amp-overview.md

@@ -497,4 +497,4 @@ Modulus and division of unsigned integers have significantly better performance
 [C++ AMP (C++ Accelerated Massive Parallelism)](../../parallel/amp/cpp-amp-cpp-accelerated-massive-parallelism.md)<br/>
 [Lambda Expression Syntax](../../cpp/lambda-expression-syntax.md)<br/>
 [Reference (C++ AMP)](../../parallel/amp/reference/reference-cpp-amp.md)<br/>
-[Parallel Programming in Native Code Blog](https://go.microsoft.com/fwlink/p/?linkid=238472)
+[Parallel Programming in Native Code Blog](/archive/blogs/nativeconcurrency/)