Confirm merge from FromPublicMasterBranch to main to sync with https://github.com/MicrosoftDocs/cpp-docs (branch main) (#5198)

* largeaddressaware:no is not recommended for 64-bit apps

* Update connect-to-your-remote-linux-computer.md

Removing references to RSA/DSA keys due to security concerns

* Update largeaddressaware-handle-large-addresses.md

* Update largeaddressaware-handle-large-addresses.md

* Update largeaddressaware-handle-large-addresses.md

* Fixed syntax error in example message

* Update clang-tidy.md

Adding support for CMake Presets

* Update clang-tidy.md

addressing some feedback

* Update assignment-operators.md

Clarify built-in behaviour for compound assignment.
Add mention of overloaded compound assignment operators
Fixes #4745

* Update gmtime-s-gmtime32-s-gmtime64-s.md

Remove note about daylight savings time, as these functions convert from time-since-epoch to UTC, neither of which are affected by daylight savings

* Update gmtime-gmtime32-gmtime64.md

* Correct JSON output of sourcedependencies.md

Updates the version number in the JSON to the one currently used by the compiler, and removes the bogus ImportedHeaderUnit entry

* update date

* Update gmtime-gmtime32-gmtime64.md

update ms.date

* Update gmtime-s-gmtime32-s-gmtime64-s.md

update date

* Update assignment-operators.md

update ms.date

* Repo sync for protected branch (#4958)

* add link to backend improvements

* change feedback system from github issues to the new UUF system (#5208)

Co-authored-by: TylerMSFT <[email protected]>

* new article: include diagnostics
* acrolinx and edit
* acrolinx
* small edits
* clarified specific to C++
* clarify that this is C++ include diagnostics
* fix github #4953

---------

Co-authored-by: TylerMSFT <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: Tyler Whitney <[email protected]>
Co-authored-by: Phil <[email protected]>
Co-authored-by: James Barnett <[email protected]>
Co-authored-by: Learn Build Service GitHub App <Learn Build Service [email protected]>

* Update clang-tidy.md

* Update clang-tidy.md

* Update clang-tidy.md

* header casing & markdown syntax tweaks

* Update docs/code-quality/clang-tidy.md

* Fix built-in operators toc yml

* Update subscript-operator.md

* Update left-shift-and-right-shift-operators-input-and-output.md

* Update subscript-operator.md

* Improve C2548 (#4964)

* Improve C2548

* Update compiler-error-c2548.md

* Update compiler-error-c2548.md

fixed title casing

* Update compiler-error-c2548.md

typo

---------

Co-authored-by: Tyler Whitney <[email protected]>

* Remove extra trailing comma in istream iterator (#4962)

* Make built-in operators title consistent (#4963)

* Fixes #3014 (#5221)

Co-authored-by: TylerMSFT <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>

---------

Co-authored-by: mspll <[email protected]>
Co-authored-by: Sinem Akinci <[email protected]>
Co-authored-by: Phil <[email protected]>
Co-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com>
Co-authored-by: Alma Jenks <[email protected]>
Co-authored-by: Learn Build Service GitHub App <Learn Build Service [email protected]>
Co-authored-by: Tyler Whitney <[email protected]>
Co-authored-by: Courtney Wales <[email protected]>
Co-authored-by: Jak Koke <[email protected]>
Co-authored-by: Javad Kouchakzadeh <[email protected]>
Co-authored-by: Sy Brand <[email protected]>
Co-authored-by: TylerMSFT <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: James Barnett <[email protected]>
Co-authored-by: Rageking8 <[email protected]>
Co-authored-by: Taojunshen <[email protected]>

Author: 16 people

docs/build/reference/largeaddressaware-handle-large-addresses.md

@@ -1,10 +1,9 @@
 ---
 description: "Learn more about: /LARGEADDRESSAWARE (Handle Large Addresses)"
 title: "/LARGEADDRESSAWARE (Handle Large Addresses)"
-ms.date: "11/04/2016"
+ms.date: "02/12/2024"
 f1_keywords: ["VC.Project.VCLinkerTool.LargeAddressAware", "/largeaddressaware"]
 helpviewer_keywords: ["LARGEADDRESSAWARE linker option", "-LARGEADDRESSAWARE linker option", "/LARGEADDRESSAWARE linker option"]
-ms.assetid: a29756c8-e893-47a9-9750-1f0d25359385
 ---
 # /LARGEADDRESSAWARE (Handle Large Addresses)
 
@@ -14,9 +13,11 @@ ms.assetid: a29756c8-e893-47a9-9750-1f0d25359385
 
 ## Remarks
 
-The /LARGEADDRESSAWARE option tells the linker that the application can handle addresses larger than 2 gigabytes. In the 64-bit compilers, this option is enabled by default. In the 32-bit compilers, /LARGEADDRESSAWARE:NO is enabled if /LARGEADDRESSAWARE is not otherwise specified on the linker line.
+The /LARGEADDRESSAWARE option tells the linker that the application can handle addresses larger than 2 gigabytes. In the 64-bit compilers, this option is enabled by default. In the 32-bit compilers, `/LARGEADDRESSAWARE:NO` is enabled if `/LARGEADDRESSAWARE` is not otherwise specified on the linker line.
 
-If an application was linked with /LARGEADDRESSAWARE, DUMPBIN [/HEADERS](headers.md) will display information to that effect.
+If an application was linked with `/LARGEADDRESSAWARE`, `DUMPBIN` [/HEADERS](headers.md) will display information to that effect.
+
+Linking 64-bit applications with **`/LARGEADDRESSAWARE:NO`** is not recommended because it restricts the available address space, which can result in runtime failures if the app exhausts memory. It may also prevent x64 apps from running on ARM64 systems because the emulation runtime will try to reserve 4GB of virtual address space. If the app was linked with `/LARGEADRESSAWARE:NO`, the app won't launch because it can't allocate that much address space.
 
 ### To set this linker option in the Visual Studio development environment
 

docs/build/reference/sourcedependencies.md

@@ -1,7 +1,7 @@
 ---
 title: "/sourceDependencies (Report source-level dependencies)"
 description: "Describes the /sourceDependencies compiler option in Microsoft C++."
-ms.date: 05/19/2022
+ms.date: 02/23/2024
 author: "tylermsft"
 ms.author: "twhitney"
 f1_keywords: ["/sourceDependencies"]
@@ -65,7 +65,7 @@ where `...` represents your other compiler options. This command line produces a
 
 ```JSON
 {
-    "Version": "1.1",
+    "Version": "1.2",
     "Data": {
         "Source": "F:\\Sample\\myproject\\modulee.ixx",
         "ProvidedModule": "ModuleE",
@@ -88,10 +88,6 @@ where `...` represents your other compiler options. This command line produces a
             {
                 "Header": "f:\\visual studio 16 main\\vc\\tools\\msvc\\14.29.30030\\include\\iostream",
                 "BMI": "F:\\Sample\\Outputs\\Intermediate\\HeaderUnits\\x64\\Debug\\iostream_W4L4JYGFJ3GL8OG9.ifc"
-            },
-            {
-                "Header": "f:\\visual studio 16 main\\vc\\tools\\msvc\\14.29.30030\\include\\yvals_core.h",
-                "BMI": "F:\\Sample\\Outputs\\Intermediate\\HeaderUnits\\x64\\Debug\\yvals_core.h.ifc"
             }
         ]
     }

docs/c-runtime-library/reference/gmtime-gmtime32-gmtime64.md

@@ -1,7 +1,7 @@
 ---
 title: "gmtime, _gmtime32, _gmtime64"
 description: "API reference for gmtime, _gmtime32, and _gmtime64, which convert a time_t value."
-ms.date: "10/27/2020"
+ms.date: 02/23/2024
 api_name: ["_gmtime32", "gmtime", "_gmtime64", "_o__gmtime32", "_o__gmtime64"]
 api_location: ["msvcrt.dll", "msvcr80.dll", "msvcr90.dll", "msvcr100.dll", "msvcr100_clr0400.dll", "msvcr110.dll", "msvcr110_clr0400.dll", "msvcr120.dll", "msvcr120_clr0400.dll", "ucrtbase.dll", "api-ms-win-crt-time-l1-1-0.dll"]
 api_type: ["DLLExport"]
@@ -54,9 +54,6 @@ These functions validate their parameters. If *`sourceTime`* is a `NULL` pointer
 
 The **`_gmtime32`** function breaks down the *`sourceTime`* value and stores it in a statically allocated structure of type `tm`, defined in `TIME.H`. The value of *`sourceTime`* is typically obtained from a call to the [`time`](time-time32-time64.md) function.
 
-> [!NOTE]
-> In most cases, the target environment tries to determine whether daylight savings time is in effect. The C run-time library assumes that the United States rules for implementing the calculation of Daylight Saving Time (DST) are used.
-
 By default, this function's global state is scoped to the application. To change this behavior, see [Global state in the CRT](../global-state.md).
 
 ## Requirements

docs/c-runtime-library/reference/gmtime-s-gmtime32-s-gmtime64-s.md

@@ -1,7 +1,7 @@
 ---
 description: "Learn more about: gmtime_s, _gmtime32_s, _gmtime64_s"
 title: "gmtime_s, _gmtime32_s, _gmtime64_s"
-ms.date: "4/2/2020"
+ms.date: 02/23/2024
 api_name: ["_gmtime32_s", "gmtime_s", "_gmtime64_s", "_o__gmtime32_s", "_o__gmtime64_s"]
 api_location: ["msvcrt.dll", "msvcr80.dll", "msvcr90.dll", "msvcr100.dll", "msvcr100_clr0400.dll", "msvcr110.dll", "msvcr110_clr0400.dll", "msvcr120.dll", "msvcr120_clr0400.dll", "ucrtbase.dll", "api-ms-win-crt-time-l1-1-0.dll"]
 api_type: ["DLLExport"]
@@ -56,9 +56,6 @@ The first two error conditions invoke the invalid parameter handler, as describe
 
 The **`_gmtime32_s`** function breaks down the *`sourceTime`* value and stores it in a structure of type `tm`, defined in `Time.h`. The address of the structure is passed in *`tmDest`*. The value of *`sourceTime`* is often obtained from a call to the [`time`](time-time32-time64.md) function.
 
-> [!NOTE]
-> The target environment should try to determine whether daylight savings time is in effect. The C run-time library assumes the United States rules for implementing the calculation of daylight saving time .
-
 Each of the structure fields is of type **`int`**, as shown in the following table.
 
 | Field | Description |

docs/code-quality/clang-tidy.md

@@ -31,14 +31,58 @@ For more information, see [How to: Set Code Analysis Properties for C/C++ Projec
 
 ## CMake
 
-In CMake projects, you can configure Clang-Tidy checks within *`CMakeSettings.json`*. Once opened, select "Edit JSON" in the top right-hand corner of the CMake Project Settings Editor. The following keys are recognized:
+In CMake projects, you can configure Clang-Tidy checks within *`CMakeSettings.json`* or *`CMakePresets.json`*. 
+
+Clang-Tidy recognizes the following keys:
 
 - `enableMicrosoftCodeAnalysis`: Enables Microsoft Code Analysis
 - `enableClangTidyCodeAnalysis`: Enables Clang-Tidy analysis
-- `clangTidyChecks`: Clang-Tidy configuration, specified as a comma-separated list, that is, checks to be enabled or disabled
+- `clangTidyChecks`: Clang-Tidy configuration. A comma-separated list of checks to enable or disable. A leading `-` disables the check. For example, "cert-oop58-cpp, -cppcoreguidelines-no-malloc, google-runtime-int" enables `cert-oop58-cpp` and `google-runtime-int`, but disables `cppcoreguidelines-no-malloc`.
 
 If neither of the "enable" options are specified, Visual Studio will select the analysis tool matching the Platform Toolset used.
 
+### CMake settings
+
+To edit your Clang-Tidy settings, open your CMake settings, and select **Edit JSON** in the CMake Project Settings Editor. You can use the keys above to fill out your Clang-Tidy specifications in the CMake Settings json file. 
+
+An example CMake settings implementation looks like this:
+
+```json
+{
+  "configurations": [
+  {
+    "name": "x64-debug",
+    "generator": "Ninja",
+    ....
+   "clangTidyChecks": "llvm-include-order, -modernize-use-override",
+   "enableMicrosoftCodeAnalysis": true,
+   "enableClangTidyCodeAnalysis": true
+  }
+  ]
+}
+```
+
+### CMake presets
+
+The same keys can be used in your CMake presets via the `vendor` object.
+
+An example CMake preset implementation looks like this:
+
+```json
+"configurePreset": [
+{ "name": "base",
+  ....
+  "vendor": {
+    "microsoft.com/VisualStudioSettings/CMake/1.0": {
+      "clangTidyChecks": "llvm-include-order, -modernize-use-override",
+      "enableMicrosoftCodeAnalysis": true,
+      "enableClangTidyCodeAnalysis": true
+      }
+    }
+}
+]
+```
+
 ## Warning display
 
 Clang-Tidy runs result in warnings displayed in the Error List, and as in-editor squiggles underneath relevant sections of code. Use the "Category" column in the Error List to sort and organize Clang-Tidy warnings. You can configure in-editor warnings by toggling the "Disable Code Analysis Squiggles" setting under **Tools** > **Options**.

docs/cpp/additive-operators-plus-and.md

@@ -6,7 +6,7 @@ f1_keywords: ["+", "-"]
 helpviewer_keywords: ["operators [C++], addition", "subtraction operator [C++], additive operators", "+ operator [C++], additive operators", "additive operators [C++]", "arithmetic operators [C++], additive operators", "- operator [C++], additive operators in C++"]
 ms.assetid: d4afafe7-e201-4c69-a649-37f17756e784
 ---
-# Additive Operators: + and -
+# Additive Operators: `+` and `-`
 
 ## Syntax
 
@@ -102,6 +102,6 @@ One of the operands can be of integral type, as long as it is the second operand
 
 ## See also
 
-[Expressions with Binary Operators](../cpp/expressions-with-binary-operators.md)<br/>
-[C++ Built-in Operators, Precedence and Associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)<br/>
+[Expressions with Binary Operators](../cpp/expressions-with-binary-operators.md)\
+[C++ Built-in Operators, Precedence and Associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)\
 [C Additive Operators](../c-language/c-additive-operators.md)

docs/cpp/assignment-operators.md

@@ -1,7 +1,7 @@
 ---
 title: "Assignment operators"
 description: "The C++ standard language assignment operators syntax and use."
-ms.date: 07/24/2020
+ms.date: 02/23/2024
 f1_keywords: ["=", "*=", "/=", "%=", "+=", "-=", "<<=", ">>=", "&=", "^=", "|="]
 helpviewer_keywords: ["operators [C++], assignment", "assignment operators [C++], C++", "&= operator", "^= operator", "+= operator", ">>= operator", "|= operator", "operator>>=", "*= operator", "%= operator", "^= operator", "operator >>=", "= operator", "-= operator", "/= operator", "<<= operator"]
 ms.assetid: b028cf35-2ff1-4f14-9027-fd53ebec8aa0
@@ -83,7 +83,7 @@ The simple assignment operator (**`=`**) causes the value of the second operand
 
 Objects of **`const`** and **`volatile`** types can be assigned to l-values of types that are only **`volatile`**, or that aren't **`const`** or **`volatile`**.
 
-Assignment to objects of class type (**`struct`**, **`union`**, and **`class`** types) is performed by a function named `operator=`. The default behavior of this operator function is to perform a bitwise copy; however, this behavior can be modified using overloaded operators. For more information, see [Operator overloading](../cpp/operator-overloading.md). Class types can also have *copy assignment* and *move assignment* operators. For more information, see [Copy constructors and copy assignment operators](copy-constructors-and-copy-assignment-operators-cpp.md) and [Move constructors and move assignment operators](move-constructors-and-move-assignment-operators-cpp.md).
+Assignment to objects of class type (**`struct`**, **`union`**, and **`class`** types) is performed by a function named `operator=`. The default behavior of this operator function is to perform a member-wise copy assignment of the object's non-static data members and direct base classes; however, this behavior can be modified using overloaded operators. For more information, see [Operator overloading](../cpp/operator-overloading.md). Class types can also have *copy assignment* and *move assignment* operators. For more information, see [Copy constructors and copy assignment operators](copy-constructors-and-copy-assignment-operators-cpp.md) and [Move constructors and move assignment operators](move-constructors-and-move-assignment-operators-cpp.md).
 
 An object of any unambiguously derived class from a given base class can be assigned to an object of the base class. The reverse isn't true because there's an implicit conversion from derived class to base class, but not from base class to derived class. For example:
 
@@ -154,18 +154,20 @@ The compound assignment operators are shown in the [Assignment operators table](
 
 - a pointer, if *op* is **`+`** or **`-`**
 
-The *e1* *op*= *e2* form behaves as *e1* **`=`** *e1* *op* *e2*, but *e1* is evaluated only once.
+- a type for which there exists a matching `operator *op*=` overload for the type of *e1*
+
+The built-in *e1* *op*= *e2* form behaves as *e1* **`=`** *e1* *op* *e2*, but *e1* is evaluated only once.
 
 Compound assignment to an enumerated type generates an error message. If the left operand is of a pointer type, the right operand must be of a pointer type, or it must be a constant expression that evaluates to 0. When the left operand is of an integral type, the right operand must not be of a pointer type.
 
-## Result of assignment operators
+## Result of built-in assignment operators
 
-The assignment operators return the value of the object specified by the left operand after the assignment. The resultant type is the type of the left operand. The result of an assignment expression is always an l-value. These operators have right-to-left associativity. The left operand must be a modifiable l-value.
+The built-in assignment operators return the value of the object specified by the left operand after the assignment (and the arithmetic/logical operation in the case of compound assignment operators). The resultant type is the type of the left operand. The result of an assignment expression is always an l-value. These operators have right-to-left associativity. The left operand must be a modifiable l-value.
 
 In ANSI C, the result of an assignment expression isn't an l-value. That means the legal C++ expression `(a += b) += c` isn't allowed in C.
 
 ## See also
 
-[Expressions with binary operators](../cpp/expressions-with-binary-operators.md)<br/>
-[C++ built-in operators, precedence, and associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)<br/>
+[Expressions with binary operators](../cpp/expressions-with-binary-operators.md)\
+[C++ built-in operators, precedence, and associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)\
 [C assignment operators](../c-language/c-assignment-operators.md)

docs/cpp/bitwise-exclusive-or-operator-hat.md

@@ -6,7 +6,7 @@ f1_keywords: ["xor_cpp", "^"]
 helpviewer_keywords: ["operators [C++], bitwise", "exclusive OR operator", "XOR operator", "bitwise operators [C++], OR operator", "^ operator", "OR operator [C++], bitwise exclusive", "operators [C++], logical"]
 ms.assetid: f9185d85-65d5-4f64-a6d6-679758d52217
 ---
-# Bitwise exclusive OR operator: ^
+# Bitwise exclusive OR operator: `^`
 
 ## Syntax
 

docs/cpp/bitwise-inclusive-or-operator-pipe.md

@@ -41,5 +41,5 @@ int main() {
 
 ## See also
 
-[C++ built-in operators, precedence, and associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)<br/>
+[C++ built-in operators, precedence, and associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)\
 [C bitwise operators](../c-language/c-bitwise-operators.md)

docs/cpp/comma-operator.md

@@ -6,7 +6,7 @@ f1_keywords: ["%2C"]
 helpviewer_keywords: ["comma operator"]
 ms.assetid: 38e0238e-19da-42ba-ae62-277bfdab6090
 ---
-# Comma Operator: ,
+# Comma Operator: `,`
 
 Allows grouping two statements where one is expected.
 
@@ -55,6 +55,6 @@ int main () {
 
 ## See also
 
-[Expressions with Binary Operators](../cpp/expressions-with-binary-operators.md)<br/>
-[C++ Built-in Operators, Precedence and Associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)<br/>
+[Expressions with Binary Operators](../cpp/expressions-with-binary-operators.md)\
+[C++ Built-in Operators, Precedence and Associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)\
 [Sequential-Evaluation Operator](../c-language/sequential-evaluation-operator.md)

docs/cpp/conditional-operator-q.md

@@ -63,5 +63,5 @@ int main() {
 
 ## See also
 
-[C++ Built-in Operators, Precedence and Associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)<br/>
+[C++ Built-in Operators, Precedence and Associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)\
 [Conditional-Expression Operator](../c-language/conditional-expression-operator.md)

docs/cpp/equality-operators-equal-equal-and-exclpt-equal.md

@@ -6,7 +6,7 @@ f1_keywords: ["!=", "==", "not_eq_cpp"]
 helpviewer_keywords: ["!= operator", "equality operator", "not equal to comparison operator", "equality operator [C++], syntax", "== operator", "not_eq operator", "equal to operator"]
 ms.assetid: ba4e9659-2392-4fb4-be5a-910a2a6df45a
 ---
-# Equality operators: == and !=
+# Equality operators: `==` and `!=`
 
 ## Syntax
 
@@ -47,6 +47,6 @@ Equality operators can compare pointers to members of the same type. In such a c
 
 ## See also
 
-[Expressions with binary operators](../cpp/expressions-with-binary-operators.md)<br/>
-[C++ built-in operators, precedence; and associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)<br/>
+[Expressions with binary operators](../cpp/expressions-with-binary-operators.md)\
+[C++ built-in operators, precedence; and associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)\
 [C relational and equality operators](../c-language/c-relational-and-equality-operators.md)

docs/cpp/explicit-type-conversion-operator-parens.md

@@ -5,7 +5,7 @@ ms.date: "11/04/2016"
 helpviewer_keywords: ["explicit data type conversion operator", "conversions [C++], explicit", "operators [C++], explicit type conversion", "data type conversion [C++], explicit", "type conversion [C++], explicit conversions"]
 ms.assetid: 54272006-5ffb-45ed-8283-27152ab97529
 ---
-# Explicit Type Conversion Operator: ()
+# Explicit Type Conversion Operator: `()`
 
 C++ allows explicit type conversion using syntax similar to the function-call syntax.
 
@@ -117,5 +117,5 @@ Type definition within casts is illegal.
 
 ## See also
 
-[Postfix Expressions](../cpp/postfix-expressions.md)<br/>
+[Postfix Expressions](../cpp/postfix-expressions.md)\
 [C++ Built-in Operators, Precedence and Associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)

docs/cpp/function-call-operator-parens.md

@@ -6,7 +6,7 @@ helpviewer_keywords: ["( ) function call operator", "function calls, C++ functio
 ms.assetid: 50c92e59-a4bf-415a-a6ab-d66c679ee80a
 no-loc: [ opt ]
 ---
-# Function Call Operator: ()
+# Function Call Operator: `()`
 
 A function call is a kind of *`postfix-expression`*, formed by an expression that evaluates to a function or callable object followed by the function-call operator, **`()`**. An object can declare an `operator ()` function, which provides function call semantics for the object.
 
@@ -172,6 +172,6 @@ Functions can be called recursively. For more information about function declara
 
 ## See also
 
-[Postfix expressions](../cpp/postfix-expressions.md)<br/>
-[C++ built-in operators, precedence, and associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)<br/>
+[Postfix expressions](../cpp/postfix-expressions.md)\
+[C++ built-in operators, precedence, and associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)\
 [Function call](../c-language/function-call-c.md)