Merge pull request #6067 from MicrosoftDocs/main

Auto Publish – main to live - 2025-09-04 17:30 UTC

Author: learn-build-service-prod[bot]

docs/error-messages/compiler-warnings/c4834.md

@@ -30,7 +30,7 @@ To turn off the warning for an entire project in the Visual Studio IDE:
 
 ## Example
 
-This sample generates C4834, and shows four ways to fix it:
+This example generates C4834, and shows four ways to fix it:
 
 ```cpp
 // C4834.cpp

docs/error-messages/compiler-warnings/c4841.md

@@ -1,6 +1,6 @@
 ---
-description: "Learn more about: Compiler Warning (level 4) C4841"
 title: "Compiler Warning (level 4) C4841"
+description: "Learn more about: Compiler Warning (level 4) C4841"
 ms.date: 05/03/2021
 f1_keywords: ["C4841"]
 helpviewer_keywords: ["C4841"]

docs/error-messages/compiler-warnings/c4843.md

@@ -1,6 +1,6 @@
 ---
-description: "Learn more about: Compiler Warning (level 4) C4843"
 title: "Compiler Warning (level 4) C4843"
+description: "Learn more about: Compiler Warning (level 4) C4843"
 ms.date: 05/03/2021
 f1_keywords: ["C4843"]
 helpviewer_keywords: ["C4843"]
@@ -17,7 +17,7 @@ This warning is new in Visual Studio 2017 version 15.5. For information on how t
 
 ## Example
 
-This sample shows several **`catch`** statements that cause C4843:
+This example shows several **`catch`** statements that cause C4843:
 
 ```cpp
 // C4843_warning.cpp

docs/error-messages/compiler-warnings/c4866.md

@@ -1,7 +1,7 @@
 ---
-description: "Learn more about: Compiler Warning (level 4) C4866"
 title: "Compiler Warning (Level 4) C4866"
-ms.date: "09/30/2018"
+description: "Learn more about: Compiler Warning (level 4) C4866"
+ms.date: 09/30/2018
 f1_keywords: ["C4866"]
 helpviewer_keywords: ["C4866"]
 ---
@@ -25,11 +25,11 @@ This warning was introduced in Visual Studio 2017 version 15.9 as a result of co
 
 To resolve this warning, first consider whether left-to-right evaluation of the operator elements is necessary, such as when evaluation of the elements might produce order-dependent side-effects. In many cases, the order in which elements are evaluated does not have an observable effect.
 
-If the order of evaluation must be left-to-right, consider whether you can pass the elements by **`const`** reference instead. This change eliminates the warning in the following code sample.
+If the order of evaluation must be left-to-right, consider whether you can pass the elements by **`const`** reference instead. This change eliminates the warning in the following code example.
 
 ## Example
 
-This sample generates C4866, and shows a way to fix it:
+This example generates C4866, and shows a way to fix it:
 
 ```cpp
 // C4866.cpp

docs/error-messages/compiler-warnings/compiler-warning-c4746.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Compiler Warning C4746"
 title: "Compiler Warning C4746"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Warning C4746"
+ms.date: 11/04/2016
 f1_keywords: ["C4746"]
 helpviewer_keywords: ["C4746"]
-ms.assetid: 5e79ab46-6031-499a-a986-716c866b6c0e
 ---
 # Compiler Warning C4746
 
-volatile access of '\<expression>' is subject to /volatile:[iso\|ms] setting; consider using __iso_volatile_load/store intrinsic functions.
+> volatile access of '\<expression>' is subject to /volatile:[iso\|ms] setting; consider using __iso_volatile_load/store intrinsic functions.
+
+## Remarks
 
 C4746 is emitted whenever a volatile variable is accessed directly. It's intended to help developers identify code locations that are affected by the specific volatile model currently specified (which can be controlled with the [`/volatile`](../../build/reference/volatile-volatile-keyword-interpretation.md) compiler option). In particular, it can be useful in locating compiler-generated hardware memory barriers when `/volatile:ms` is used.
 

docs/error-messages/compiler-warnings/compiler-warning-c4867.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Compiler Warning C4867"
 title: "Compiler Warning C4867"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Warning C4867"
+ms.date: 11/04/2016
 f1_keywords: ["C4867"]
 helpviewer_keywords: ["C4867"]
-ms.assetid: 8a257d70-c3a7-462d-b285-e57c952a8bf7
 ---
 # Compiler Warning C4867
 
-'function': function call missing argument list; use 'call' to create a pointer to member
+> 'function': function call missing argument list; use 'call' to create a pointer to member
+
+## Remarks
 
 A pointer to member function was initialized incorrectly.
 
@@ -18,7 +19,7 @@ This warning is always issued as an error. Use the [warning](../../preprocessor/
 
 ## Example
 
-The following sample generates C4867.
+The following example generates C4867.
 
 ```cpp
 // C4867.cpp

docs/error-messages/compiler-warnings/compiler-warning-c4868.md

@@ -1,15 +1,16 @@
 ---
-description: "Learn more about: Compiler Warning (level 4) C4868"
 title: "Compiler Warning C4868"
-ms.date: "10/26/2017"
+description: "Learn more about: Compiler Warning (level 4) C4868"
+ms.date: 10/26/2017
 f1_keywords: ["C4868"]
 helpviewer_keywords: ["C4868"]
-ms.assetid: fc6aa7e5-34dd-4ec2-88bd-16e430361dc7
 ---
 # Compiler Warning (level 4) C4868
 
 > '_file_(*line_number*)' compiler may not enforce left-to-right evaluation order in braced initializer list
 
+## Remarks
+
 The elements of a braced initializer list are to be evaluated in left-to-right order. There are two cases in which the compiler is unable to guarantee this order: the first is when some of the elements are objects passed by value; the second is  when compiling with `/clr` and some of the elements are fields of objects or are array elements. When the compiler can't guarantee left-to-right evaluation it emits warning C4868.
 
 This warning can be generated as a result of compiler conformance work that was done for Visual Studio 2015 Update 2. Code that compiled prior to Visual Studio 2015 Update 2 can now generate C4868.
@@ -18,11 +19,11 @@ This warning is off by default. Use `/Wall` to activate this warning.
 
 To resolve this warning, first consider whether left-to-right evaluation of the initializer list elements is necessary, such as when evaluation of the elements might produce order-dependent side-effects. In many cases, the order in which elements are evaluated does not have an observable effect.
 
-If the order of evaluation must be left-to-right, consider if it's possible to pass the elements by **`const`** reference instead. A change such as this eliminates the warning in the following code sample.
+If the order of evaluation must be left-to-right, consider if it's possible to pass the elements by **`const`** reference instead. A change such as this eliminates the warning in the following code example.
 
 ## Example
 
-This sample generates C4868, and shows a way to fix it:
+This example generates C4868, and shows a way to fix it:
 
 ```cpp
 // C4868.cpp

docs/error-messages/compiler-warnings/compiler-warning-c4936.md

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: Compiler Warning C4936"
 title: "Compiler Warning C4936"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Warning C4936"
+ms.date: 11/04/2016
 f1_keywords: ["C4936"]
 helpviewer_keywords: ["C4936"]
-ms.assetid: 6676de35-bf1b-4d0b-a70f-b5734130336c
 ---
 # Compiler Warning C4936
 
@@ -22,7 +21,7 @@ C4936 is always issued as an error.  You can disable C4936 with the [warning](..
 
 ## Example
 
-The following sample generates C4936:
+The following example generates C4936:
 
 ```cpp
 // C4936.cpp

docs/error-messages/compiler-warnings/compiler-warning-level-1-c4711.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Compiler Warning (level 1) C4711"
 title: "Compiler Warning (level 1) C4711"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Warning (level 1) C4711"
+ms.date: 11/04/2016
 f1_keywords: ["C4711"]
 helpviewer_keywords: ["C4711"]
-ms.assetid: 270506ab-fead-4328-b714-2978113be238
 ---
 # Compiler Warning (level 1) C4711
 
-function 'function' selected for inline expansion
+> function 'function' selected for inline expansion
+
+## Remarks
 
 The compiler performed inlining on the given function, although it was not marked for inlining.
 

docs/error-messages/compiler-warnings/compiler-warning-level-1-c4715.md

@@ -1,19 +1,22 @@
 ---
-description: "Learn more about: Compiler Warning (level 1) C4715"
 title: "Compiler Warning (level 1) C4715"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Warning (level 1) C4715"
+ms.date: 11/04/2016
 f1_keywords: ["C4715"]
 helpviewer_keywords: ["C4715"]
-ms.assetid: 1c819bf7-0d8b-4f5e-b338-9cc292870439
 ---
 # Compiler Warning (level 1) C4715
 
-'function' : not all control paths return a value
+> 'function' : not all control paths return a value
+
+## Remarks
 
 The specified function can potentially not return a value.
 
 ## Example
 
+The following example generates C4715:
+
 ```cpp
 // C4715a.cpp
 // compile with: /W1 /LD