Merge pull request #5938 from MicrosoftDocs/FromPublicMasterBranch

Albertyang0 · web-flow · commit 9cc946da656c · 2025-05-28T10:04:27.000-07:00
Confirm merge from FromPublicMasterBranch to main to sync with https://github.com/MicrosoftDocs/cpp-docs (branch main)
diff --git a/docs/build/clang-support-msbuild.md b/docs/build/clang-support-msbuild.md
@@ -57,7 +57,7 @@ To configure a Visual Studio project to use Clang, right-click on the project no
 The project properties page is open to the Configuration Properties > General page. The Platform Toolset dropdown is selected, on which LLVM (clang-cl) is selected.
 :::image-end:::
 
-If you're using the Clang tools that are bundled with Visual Studio, no extra steps are required. For Windows projects, Visual Studio by default invokes Clang in [clang-cl](https://llvm.org/devmtg/2014-04/PDFs/Talks/clang-cl.pdf) mode. It links with the Microsoft implementation of the Standard Library. By default, **clang-cl.exe** is located in `*%VCINSTALLDIR%\Tools\Llvm\bin\*` and `*%VCINSTALLDIR%\Tools\Llvm\x64\bin\*`.
+If you're using the Clang tools that are bundled with Visual Studio, no extra steps are required. For Windows projects, Visual Studio by default invokes Clang in [clang-cl](https://llvm.org/devmtg/2014-04/PDFs/Talks/clang-cl.pdf) mode. It links with the Microsoft implementation of the Standard Library. By default, **clang-cl.exe** is located in *`%VCINSTALLDIR%\Tools\Llvm\bin\`* and *`%VCINSTALLDIR%\Tools\Llvm\x64\bin\`*.
 
 If you're using a custom Clang installation, you can change the value of the `LLVMInstallDir` property. For more information, see [Set a custom LLVM location](#custom_llvm_location).
 
diff --git a/docs/build/launch-vs-schema-reference-cpp.md b/docs/build/launch-vs-schema-reference-cpp.md
@@ -55,7 +55,7 @@ To create the file, right-click on an executable file in **Solution Explorer** a
 | `debugServerArgs` | string | Optional debug server args. Defaults to null. |
 | `filterStderr` | boolean | Search stderr stream for server-started pattern and log stderr to debug output. Defaults to **`false`**. |
 | `coreDumpPath` | string | Optional full path to a core dump file for the specified program. Defaults to null. |
-| externalConsole | boolean | If true, a console is launched for the debuggee. If **`false`**, no console is launched. The default for this setting is **`false`**. This option is ignored in some cases for technical reasons. |
+| `externalConsole` | boolean | If true, a console is launched for the debuggee. If **`false`**, no console is launched. The default for this setting is **`false`**. This option is ignored in some cases for technical reasons. |
 | `pipeTransport` | string | When present, this value tells the debugger to connect to a remote computer using another executable as a pipe that will relay standard input/output between Visual Studio and the MI-enabled debugger (such as gdb). Allowed values: one or more [Pipe Transport Options](#pipe_transport_options). |
 
 ## debugInfo macros
diff --git a/docs/build/reference/arch-arm64.md b/docs/build/reference/arch-arm64.md
@@ -25,7 +25,7 @@ Specifies the Armv9-A architecture, where **`x`** is a required extension value
 You can specify an ARM64 extension from Armv8.0-A through Armv8.9-A, and Armv9.0-A through Armv9.4-A. Optionally, enable one or more architecture features by appending a feature argument to the option<sup>3</sup>. For example, to target Armv8.0-A and enable feature `FEAT_LSE`, append feature argument **`lse`** so that the option becomes **`/arch:armv8.0+lse`**. For more information about available features and their requirements, see [`/feature` (ARM64)](feature-arm64.md)<sup>3</sup>.
 
 > [!NOTE]
-> Depending on your version of Visual Studio, the compiler may not yet generate instructions from all feature sets required by the extension level you specify. For example, **`/arch:armv8.1`** allows the `*Interlocked*` intrinsic functions to use the appropriate atomic instruction introduced with the Armv8.1-A extension feature `FEAT_LSE`, but compiler support requires Visual Studio 2022 version 17.2 or later.
+> Depending on your version of Visual Studio, the compiler may not yet generate instructions from all feature sets required by the extension level you specify. For example, **`/arch:armv8.1`** allows the *`Interlocked`* intrinsic functions to use the appropriate atomic instruction introduced with the Armv8.1-A extension feature `FEAT_LSE`, but compiler support requires Visual Studio 2022 version 17.2 or later.
 
 The `_M_ARM64` macro is defined by default when compiling for an ARM64 target. For more information, see [Predefined macros](../../preprocessor/predefined-macros.md).
 
diff --git a/docs/build/reference/ifc-map.md b/docs/build/reference/ifc-map.md
@@ -17,7 +17,7 @@ This switch tells the compiler where to find the IFC reference map file, which m
 
 ## Remarks
 
-The `*filename*` argument specifies the IFC reference map file. It can be relative to the compiler's working directory, or an absolute path.
+The *`filename`* argument specifies the IFC reference map file. It can be relative to the compiler's working directory, or an absolute path.
 
 You can provide multiple `/ifcMap` arguments to the compiler.
 
diff --git a/docs/build/walkthrough-import-stl-header-units.md b/docs/build/walkthrough-import-stl-header-units.md
@@ -182,8 +182,8 @@ Follow these steps to create a project that includes two STL libraries: `<iostre
 1. Replace the contents of the source file as follows:
 
     ```cpp
-    #include <iostream>;
-    #include <vector>;
+    #include <iostream>
+    #include <vector>
     
     int main()
     {
diff --git a/docs/code-quality/c26434.md b/docs/code-quality/c26434.md
@@ -4,7 +4,6 @@ description: "Microsoft C++ Code Analysis warning C26434 for the C++ Core Guidel
 ms.date: 08/21/2020
 f1_keywords: ["C26434", "DONT_HIDE_METHODS"]
 helpviewer_keywords: ["C26434"]
-ms.assetid: 7f66477f-da66-444a-a6e3-44513d7d7e31
 ---
 # Warning C26434
 
@@ -44,5 +43,4 @@ struct Derived : Base
     void not_virtual() noexcept {}              // C26434, hides a non-virtual function
     virtual void not_virtual(int i) noexcept {} // C26434, and parameters ignored
 };
-
 ```
diff --git a/docs/code-quality/c26483.md b/docs/code-quality/c26483.md
@@ -1,9 +1,9 @@
 ---
 title: Warning C26483
+description: CppCoreCheck rule C26483 that enforces C++ Core Guidelines Bounds.2
 ms.date: 03/22/2018
 f1_keywords: ["C26483", "STATIC_INDEX_OUT_OF_RANGE"]
 helpviewer_keywords: ["C26483"]
-description: CppCoreCheck rule C26483 that enforces C++ Core Guidelines Bounds.2
 ---
 # Warning C26483
 
@@ -24,5 +24,4 @@ void function()
     int arr2[] { 1, 2, 3 };
     arr2[3] = 4; // C26483, 3 is outside the bounds of the array
 }
-
 ```
diff --git a/docs/code-quality/c28159.md b/docs/code-quality/c28159.md
@@ -1,14 +1,13 @@
 ---
-description: "Learn more about: Warning C28159"
 title: Warning C28159
+description: "Learn more about: Warning C28159"
 ms.date: 09/08/2022
 f1_keywords: ["C28159", "USE_OTHER_FUNCTION", "__WARNING_USE_OTHER_FUNCTION"]
 helpviewer_keywords: ["C28159"]
-ms.assetid: fab6cd58-0985-4ef6-89a2-64ed04297437
 ---
 # Warning C28159
 
-> Consider using `*function_name_1*` instead of `*function_name_2*`. Reason: *reason*
+> Consider using *`function_name_1`* instead of *`function_name_2`*. Reason: *reason*
 
 This warning occurs when you use a function that is semantically equivalent to an alternative, preferred function call.
 
diff --git a/docs/code-quality/c6331.md b/docs/code-quality/c6331.md
@@ -1,14 +1,13 @@
 ---
-description: "Learn more about: Warning C6331"
 title: Warning C6331
+description: "Learn more about: Warning C6331"
 ms.date: 10/03/2022
 f1_keywords: ["C6331", "VirtualFreeInvalidParam1", "__WARNING_VIRTUALFREEINVALIDPARAM1"]
 helpviewer_keywords: ["C6331"]
-ms.assetid: cb1ecc2c-29a5-4c57-acf2-0954a4c047b1
 ---
 # Warning C6331
 
-> Invalid parameter: passing MEM_RELEASE and MEM_DECOMMIT in conjunction to `*function*` is not allowed. This results in the failure of this call
+> Invalid parameter: passing MEM_RELEASE and MEM_DECOMMIT in conjunction to *`function`* is not allowed. This results in the failure of this call
 
 This message indicates that an invalid parameter is passed to `VirtualFree` or `VirtualFreeEx`. `VirtualFree` and `VirtualFreeEx` both reject the flags (`MEM_RELEASE | MEM_DECOMMIT`) in combination. Therefore, the values `MEM_DECOMMIT` and `MEM_RELEASE` may not be used together in the same call.
 
diff --git a/docs/code-quality/c6383.md b/docs/code-quality/c6383.md
@@ -1,14 +1,13 @@
 ---
-description: "Learn more about: Warning C6383"
 title: Warning C6383
+description: "Learn more about: Warning C6383"
 ms.date: 09/07/2022
 f1_keywords: ["C6383", "ELEMENTS_TO_BYTES", "__WARNING_ELEMENTS_TO_BYTES"]
 helpviewer_keywords: ["C6383"]
-ms.assetid: f5ff7938-0fbe-4b71-b98f-098fe887799d
 ---
 # Warning C6383
 
-> Buffer overrun due to conversion of an element count into a byte count: an element count is expected for parameter `*parameter_name*` in call to `*function_name*`
+> Buffer overrun due to conversion of an element count into a byte count: an element count is expected for parameter *`parameter_name`* in call to *`function_name`*
 
 This warning indicates that a non-constant byte count is being passed when an element count is instead required.
 
diff --git a/docs/cpp/cpp-language-reference.md b/docs/cpp/cpp-language-reference.md
@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: C++ Language Reference"
 title: "C++ Language Reference"
+description: "Learn more about: C++ Language Reference"
 ms.custom: "index-page"
-ms.date: "12/10/2019"
+ms.date: 12/10/2019
 helpviewer_keywords: ["C++, language reference"]
-ms.assetid: 4be9cacb-c862-4391-894a-3a118c9c93ce
 ---
 # C++ Language Reference
 
@@ -14,96 +13,95 @@ For an overview of Modern C++ programming practices, see [Welcome Back to C++](w
 
 See the following tables to quickly find a keyword or operator:
 
-- [C++ Keywords](../cpp/keywords-cpp.md)
-
-- [C++ Operators](../cpp/cpp-built-in-operators-precedence-and-associativity.md)
+- [C++ Keywords](keywords-cpp.md)
+- [C++ Operators](cpp-built-in-operators-precedence-and-associativity.md)
 
 ## In This Section
 
-[Lexical Conventions](../cpp/lexical-conventions.md)<br/>
+[Lexical Conventions](lexical-conventions.md)\
 Fundamental lexical elements of a C++ program: tokens, comments, operators, keywords, punctuators, literals. Also, file translation, operator precedence/associativity.
 
-[Basic Concepts](../cpp/basic-concepts-cpp.md)<br/>
+[Basic Concepts](basic-concepts-cpp.md)\
 Scope, linkage, program startup and termination, storage classes, and types.
 
-[Built-in types](fundamental-types-cpp.md)
+[Built-in types](fundamental-types-cpp.md)\
 The fundamental types that are built into the C++ compiler and their value ranges.
 
-[Standard Conversions](../cpp/standard-conversions.md)<br/>
+[Standard Conversions](standard-conversions.md)\
 Type conversions between built-in types. Also, arithmetic conversions and conversions among pointer, reference, and pointer-to-member types.
 
-[Declarations and definitions](declarations-and-definitions-cpp.md)
+[Declarations and definitions](declarations-and-definitions-cpp.md)\
 Declaring and defining variables, types and functions.
 
-[Operators, Precedence and Associativity](../cpp/cpp-built-in-operators-precedence-and-associativity.md)<br/>
+[Operators, Precedence and Associativity](cpp-built-in-operators-precedence-and-associativity.md)\
 The operators in C++.
 
-[Expressions](../cpp/expressions-cpp.md)<br/>
+[Expressions](expressions-cpp.md)\
 Types of expressions, semantics of expressions, reference topics on operators, casting and casting operators, run-time type information.
 
-[Lambda Expressions](../cpp/lambda-expressions-in-cpp.md)<br/>
+[Lambda Expressions](lambda-expressions-in-cpp.md)\
 A programming technique that implicitly defines a function object class and constructs a function object of that class type.
 
-[Statements](../cpp/statements-cpp.md)<br/>
+[Statements](statements-cpp.md)\
 Expression, null, compound, selection, iteration, jump, and declaration statements.
 
-[Classes and structs](../cpp/classes-and-structs-cpp.md)<br/>
+[Classes and structs](classes-and-structs-cpp.md)\
 Introduction to classes, structures, and unions. Also, member functions, special member functions, data members, bit fields, **`this`** pointer, nested classes.
 
-[Unions](unions.md)<br/>
+[Unions](unions.md)\
 User-defined types in which all members share the same memory location.
 
-[Derived Classes](../cpp/inheritance-cpp.md)<br/>
+[Derived Classes](inheritance-cpp.md)\
 Single and multiple inheritance, **`virtual`** functions, multiple base classes, **abstract** classes, scope rules. Also, the **`__super`** and **`__interface`** keywords.
 
-[Member-Access Control](../cpp/member-access-control-cpp.md)<br/>
+[Member-Access Control](member-access-control-cpp.md)\
 Controlling access to class members: **`public`**, **`private`**, and **`protected`** keywords. Friend functions and classes.
 
-[Overloading](operator-overloading.md)<br/>
+[Overloading](operator-overloading.md)\
 Overloaded operators, rules for operator overloading.
 
-[Exception Handling](../cpp/exception-handling-in-visual-cpp.md)<br/>
+[Exception Handling](exception-handling-in-visual-cpp.md)\
 C++ exception handling, structured exception handling (SEH), keywords used in writing exception handling statements.
 
-[Assertion and User-Supplied Messages](../cpp/assertion-and-user-supplied-messages-cpp.md)<br/>
+[Assertion and User-Supplied Messages](assertion-and-user-supplied-messages-cpp.md)\
 `#error` directive, the **`static_assert`** keyword, the `assert` macro.
 
-[Templates](../cpp/templates-cpp.md)<br/>
+[Templates](templates-cpp.md)\
 Template specifications, function templates, class templates, **`typename`** keyword, templates vs. macros, templates and smart pointers.
 
-[Event Handling](../cpp/event-handling.md)<br/>
+[Event Handling](event-handling.md)\
 Declaring events and event handlers.
 
-[Microsoft-Specific Modifiers](../cpp/microsoft-specific-modifiers.md)<br/>
+[Microsoft-Specific Modifiers](microsoft-specific-modifiers.md)\
 Modifiers specific to Microsoft C++. Memory addressing, calling conventions, **`naked`** functions, extended storage-class attributes (**`__declspec`**), **`__w64`**.
 
-[Inline Assembler](../assembler/inline/inline-assembler.md)<br/>
+[Inline Assembler](../assembler/inline/inline-assembler.md)\
 Using assembly language and C++ in **`__asm`** blocks.
 
-[Compiler COM Support](../cpp/compiler-com-support.md)<br/>
+[Compiler COM Support](compiler-com-support.md)\
 A reference to Microsoft-specific classes and global functions used to support COM types.
 
-[Microsoft Extensions](../cpp/microsoft-extensions.md)<br/>
+[Microsoft Extensions](microsoft-extensions.md)\
 Microsoft extensions to C++.
 
-[Nonstandard Behavior](../cpp/nonstandard-behavior.md)<br/>
+[Nonstandard Behavior](nonstandard-behavior.md)\
 Information about nonstandard behavior of the Microsoft C++ compiler.
 
-[Welcome Back to C++](welcome-back-to-cpp-modern-cpp.md)<br/>
+[Welcome Back to C++](welcome-back-to-cpp-modern-cpp.md)\
 An overview of modern C++ programming practices for writing safe, correct and efficient programs.
 
 ## Related Sections
 
-[Component Extensions for Runtime Platforms](../extensions/component-extensions-for-runtime-platforms.md)<br/>
+[Component Extensions for Runtime Platforms](../extensions/component-extensions-for-runtime-platforms.md)\
 Reference material on using the Microsoft C++ compiler to target .NET.
 
-[C/C++ Building Reference](../build/reference/c-cpp-building-reference.md)<br/>
+[C/C++ Building Reference](../build/reference/c-cpp-building-reference.md)\
 Compiler options, linker options, and other build tools.
 
-[C/C++ Preprocessor Reference](../preprocessor/c-cpp-preprocessor-reference.md)<br/>
+[C/C++ Preprocessor Reference](../preprocessor/c-cpp-preprocessor-reference.md)\
 Reference material on pragmas, preprocessor directives, predefined macros, and the preprocessor.
 
-[Visual C++ Libraries](../standard-library/cpp-standard-library-reference.md)<br/>
+[Visual C++ Libraries](../standard-library/cpp-standard-library-reference.md)\
 A list of links to the reference start pages for the various Microsoft C++ libraries.
 
 ## See also
diff --git a/docs/cppcx/crt-functions-not-supported-in-universal-windows-platform-apps.md b/docs/cppcx/crt-functions-not-supported-in-universal-windows-platform-apps.md
@@ -1,8 +1,7 @@
 ---
 title: "CRT functions not supported in Universal Windows Platform apps"
 description: "Reference guide to CRT functions not supported in Universal Windows Platform apps."
-ms.date: "04/16/2020"
-ms.assetid: cbfc957d-6c60-48f4-97e3-1ed8526743b4
+ms.date: 04/16/2020
 ---
 # CRT functions not supported in Universal Windows Platform apps
 
@@ -47,4 +46,4 @@ Both the previously mentioned APIs and the following APIs are unavailable in Win
 |`_chdir` `_wchdir` `_getcwd` `_getdcwd` `_wgetcwd` `_wgetdcwd`|The concept of a working directory doesn't apply to Windows 8.x Store apps.|Use full paths instead.|
 |`_isleadbyte_l` `_ismbbalnum`, `_ismbbalnum_l`, `_ismbbalpha`, `_ismbbalpha` `_ismbbalpha_l` `_ismbbgraph` `_ismbbgraph_l` `_ismbbkalnum` `_ismbbkalnum_l` `_ismbbkana` `_ismbbkana_l` `_ismbbkprint` `_ismbbkprint_l` `_ismbbkpunct` `_ismbbkpunct_l` `_ismbblead` `_ismbblead_l` `_ismbbprint` `_ismbbprint_l` `_ismbbpunct` `_ismbbpunct_l` `_ismbbtrail` `_ismbbtrail_l` `_ismbslead` `_ismbslead_l` `_ismbstrail` `_ismbstrail_l` `_mbsdup` `isleadbyte`|Multi-byte strings are not supported in Windows 8.x Store apps.|Use Unicode strings instead.|
 |`_tzset`|Environment variables are not available to Windows  8.x Store apps.|No workaround.|
-|`_get_heap_handle`, `_heapmin`|The corresponding Win32 APIs are not supported in Windows 8.x Store apps. And, apps can no longer create private heaps.|No workaround. However, ``_get_heap_handle`` is available in the DEBUG CRT, for debugging purposes only.|
+|`_get_heap_handle`, `_heapmin`|The corresponding Win32 APIs are not supported in Windows 8.x Store apps. And, apps can no longer create private heaps.|No workaround. However, `_get_heap_handle` is available in the DEBUG CRT, for debugging purposes only.|
diff --git a/docs/dotnet/how-to-define-and-consume-classes-and-structs-cpp-cli.md b/docs/dotnet/how-to-define-and-consume-classes-and-structs-cpp-cli.md
@@ -466,7 +466,7 @@ in static constructor
 
 ## <a name="BKMK_Semantics_of_the_this_pointer"></a> Semantics of the `this` pointer
 
-When you're using C++\CLI to define types, the **`this`** pointer in a reference type is of type *handle*. The **`this`** pointer in a value type is of type *interior pointer*.
+When you're using C++/CLI to define types, the **`this`** pointer in a reference type is of type *handle*. The **`this`** pointer in a value type is of type *interior pointer*.
 
 These different semantics of the **`this`** pointer can cause unexpected behavior when a default indexer is called. The next example shows the correct way to access a default indexer in both a ref type and a value type.
 
diff --git a/docs/error-messages/compiler-errors-1/compiler-error-c2440.md b/docs/error-messages/compiler-errors-1/compiler-error-c2440.md
@@ -1,18 +1,17 @@
 ---
-description: "Learn about type conversion errors that cause Compiler Error C2440."
 title: "Compiler Error C2440"
+description: "Learn about type conversion errors that cause Compiler Error C2440."
 ms.date: 08/27/2021
 f1_keywords: ["C2440"]
 helpviewer_keywords: ["C2440"]
 no-loc: ["struct", "const"]
-ms.assetid: 36e6676c-f04f-4715-8ba1-f096c4bf3b44
 ---
 # Compiler Error C2440
 
 > '*initializing*' : cannot convert from '*type1*' to '*type2*'\
 > '*conversion*' : cannot convert from '*type1*' to '*type2*'
 
-The compiler can't implicitly convert from `*type1*` to `*type2*`, or can't use the specified cast or conversion operator.
+The compiler can't implicitly convert from *`type1`* to *`type2`*, or can't use the specified cast or conversion operator.
 
 ## Remarks
 
diff --git a/docs/error-messages/compiler-warnings/compiler-warning-level-2-c4150.md b/docs/error-messages/compiler-warnings/compiler-warning-level-2-c4150.md
@@ -1,7 +1,7 @@
 ---
-description: "Learn more about: Compiler Warning (level 2) C4150"
 title: Compiler warning (level 2) C4150
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Warning (level 2) C4150"
+ms.date: 11/04/2016
 f1_keywords: ["C4150"]
 helpviewer_keywords: ["C4150"]
 ---
@@ -75,7 +75,6 @@ void NoDestruct( IncClass* pIncClass )
 {
    delete pIncClass;
 }
-
 ```
 
 ## See also
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk2019.md b/docs/error-messages/tool-errors/linker-tools-error-lnk2019.md
diff --git a/docs/mfc/reference/connection-maps.md b/docs/mfc/reference/connection-maps.md
diff --git a/docs/mfc/reference/styles-used-by-mfc.md b/docs/mfc/reference/styles-used-by-mfc.md
diff --git a/docs/sanitizers/asan-continue-on-error.md b/docs/sanitizers/asan-continue-on-error.md
diff --git a/docs/standard-library/chrono-operators.md b/docs/standard-library/chrono-operators.md
diff --git a/docs/standard-library/multiset-class.md b/docs/standard-library/multiset-class.md

Original file line number	Diff line number	Diff line change
@@ -182,8 +182,8 @@ Follow these steps to create a project that includes two STL libraries: `<iostre
`182`	`182`	`1. Replace the contents of the source file as follows:`
`183`	`183`
`184`	`184`	```cpp
`185`		`- #include <iostream>;`
`186`		`- #include <vector>;`
	`185`	`+ #include <iostream>`
	`186`	`+ #include <vector>`
`187`	`187`
`188`	`188`	`int main()`
`189`	`189`	`{`