Merge branch 'master' into docs/corob/chrono-3

Author: Colin Robertson

docs/build/reference/experimental-module.md

@@ -5,7 +5,7 @@ ms.date: "04/13/2021"
 f1_keywords: ["module", "/experimental:module"]
 helpviewer_keywords: ["module", "/experimental:module", "Enable module support"]
 ---
-# /experimental:module (Enable module support)
+# `/experimental:module` (Enable module support)
 
 Enables experimental compiler support for Standard Template Library named modules.
 

docs/build/reference/fc-full-path-of-source-code-file-in-diagnostics.md

@@ -1,43 +1,53 @@
 ---
-description: "Learn more about: /FC (Full Path of Source Code File in Diagnostics)"
-title: "/FC (Full Path of Source Code File in Diagnostics)"
-ms.date: "11/04/2016"
-f1_keywords: ["VC.Project.VCCLCompilerTool.UseFullPaths", "/FC"]
+description: "Learn more about: /FC (Full path of source code file in diagnostics)"
+title: "/FC (Full path of source code file in diagnostics)"
+ms.date: 04/26/2021
+f1_keywords: ["VC.Project.VCCLCompilerTool.UseFullPaths", "/FC", "-FC"]
 helpviewer_keywords: ["/FC compiler option [C++]", "-FC compiler option [C++]"]
 ms.assetid: 1f11414e-cb42-421b-be68-9d369aab036b
 ---
-# /FC (Full Path of Source Code File in Diagnostics)
+# `/FC` (Full path of source code file in diagnostics)
 
 Causes the compiler to display the full path of source code files passed to the compiler in diagnostics.
 
 ## Syntax
 
-> /FC
+> **`/FC`**
 
 ## Remarks
 
-Consider the following code sample:
+Consider the following code sample, where the source file is located in *`C:\test\compiler_option_FC.cpp`*:
 
 ```cpp
 // compiler_option_FC.cpp
+
 int main( ) {
    int i   // C2143
 }
 ```
 
-Without **/FC**, the diagnostic text would look similar to this diagnostic text:
+Without **`/FC`**, the compiler output looks similar to this diagnostic text:
+
+- compiler_option_FC.cpp(5): error C2143: syntax error: missing ';' before '}'
+
+With **`/FC`**, the compiler output looks similar to this diagnostic text:
+
+::: moniker range="<=msvc-150"
+
+- c:\test\compiler_option_fc.cpp(5): error C2143: syntax error: missing ';' before '}'
 
-- compiler_option_FC.cpp(5) : error C2143: syntax error : missing ';' before '}'
+::: moniker-end
+::: moniker range="msvc-160"
 
-With **/FC**, the diagnostic text would look similar to this diagnostic text:
+- C:\test\compiler_option_FC.cpp(5): error C2143: syntax error: missing ';' before '}'
 
-- c:\test\compiler_option_fc.cpp(5) : error C2143: syntax error : missing ';' before '}'
+::: moniker-end
 
-**/FC** is also needed if you want to see the full path of a file name when using the &#95;&#95;FILE&#95;&#95; macro. See [Predefined Macros](../../preprocessor/predefined-macros.md) for more information on &#95;&#95;FILE&#95;&#95;.
+**`/FC`** is also needed if you want to see the full path of a file name when using the `__FILE__` macro. For more information about `__FILE__`, see [Predefined macros](../../preprocessor/predefined-macros.md).
 
-The **/FC** option is implied by **/ZI**. For more information about **/ZI**, see [/Z7, /Zi, /ZI (Debug Information Format)](z7-zi-zi-debug-information-format.md).
+The **`/FC`** option is implied by **`/ZI`**. For more information about **`/ZI`**, see [`/Z7, /Zi, /ZI` (Debug information format)](z7-zi-zi-debug-information-format.md).
 
-**/FC** outputs full paths in lower case.
+In Visual Studio 2017 and earlier versions, **`/FC`** outputs full paths in lower case. Starting in Visual Studio 2019, **`/FC`** uses the same casing as the file system for full paths.
 
 ### To set this compiler option in the Visual Studio development environment
 
@@ -47,11 +57,11 @@ The **/FC** option is implied by **/ZI**. For more information about **/ZI**, se
 
 1. Modify the **Use Full Paths** property.
 
-### To set this linker option programmatically
+### To set this compiler option programmatically
 
 - See <xref:Microsoft.VisualStudio.VCProjectEngine.VCCLCompilerTool.UseFullPaths%2A>.
 
 ## See also
 
-[MSVC Compiler Options](compiler-options.md)<br/>
-[MSVC Compiler Command-Line Syntax](compiler-command-line-syntax.md)
+[MSVC compiler options](compiler-options.md)\
+[MSVC compiler command-line syntax](compiler-command-line-syntax.md)

docs/build/reference/openmp-enable-openmp-2-0-support.md

@@ -41,7 +41,7 @@ Currently, the **`/openmp:llvm`** option only works on the x64 architecture. The
 
 Applications compiled by using both **`/openmp`** and **`/clr`** can only be run in a single application domain process. Multiple application domains aren't supported. That is, when the module constructor (`.cctor`) is run, it detects if the process is compiled using **`/openmp`**, and if the app is loaded into a non-default runtime. For more information, see [`appdomain`](../../cpp/appdomain.md), [`/clr` (Common Language Runtime Compilation)](clr-common-language-runtime-compilation.md), and [Initialization of Mixed Assemblies](../../dotnet/initialization-of-mixed-assemblies.md).
 
-If you attempt to load an app compiled using both **`/openmp`** and **`/clr*`* into a non-default application domain, a <xref:System.TypeInitializationException> exception is thrown outside the debugger, and a `OpenMPWithMultipleAppdomainsException` exception is thrown in the debugger.
+If you attempt to load an app compiled using both **`/openmp`** and **`/clr`** into a non-default application domain, a <xref:System.TypeInitializationException> exception is thrown outside the debugger, and a `OpenMPWithMultipleAppdomainsException` exception is thrown in the debugger.
 
 These exceptions can also be raised in the following situations:
 

docs/c-runtime-library/reference/splitpath-s-wsplitpath-s.md

@@ -81,7 +81,7 @@ Base filename (without extension). You can pass **NULL** for this parameter if y
 The size of the *fname* buffer in single-byte or wide characters. If *fname* is **NULL**, this value must be 0.
 
 *ext*<br/>
-Filename extension, including leading period (**.**).You can pass **NULL** for this parameter if you do not need the filename extension.
+Filename extension, including leading period (**.**). You can pass **NULL** for this parameter if you do not need the filename extension.
 
 *extNumberOfElements*<br/>
 The size of *ext* buffer in single-byte or wide characters. If *ext* is **NULL**, this value must be 0.

docs/code-quality/c6290.md

@@ -13,7 +13,7 @@ ms.assetid: 96a1acc4-724b-4b56-b091-661ddcc03884
 
 This warning indicates possible confusion in the use of an operator or an operator precedence.
 
-The `!` operator yields a Boolean result, and it has higher precedence than the `&`.The bitwise-and (&) operator takes two arithmetic arguments. Therefore, one of the following errors has been detected:
+The `!` operator yields a Boolean result, and it has higher precedence than the `&`. The bitwise-and (&) operator takes two arithmetic arguments. Therefore, one of the following errors has been detected:
 
 - The expression is mis-parenthesised:
 

docs/cpp/inheritance-cpp.md

@@ -27,7 +27,7 @@ class Derived : [virtual] [access-specifier] Base1,
 
 After the tag (name) for the class, a colon appears followed by a list of base specifications.  The base classes so named must have been declared previously.  The base specifications may contain an access specifier, which is one of the keywords **`public`**, **`protected`** or **`private`**.  These access specifiers appear before the base class name and apply only to that base class.  These specifiers control the derived class's permission to use to members of the base class.  See [Member-Access Control](../cpp/member-access-control-cpp.md) for information on access to base class members.  If the access specifier is omitted, the access to that base is considered **`private`**.  The base specifications may contain the keyword **`virtual`** to indicate virtual inheritance.  This keyword may appear before or after the access specifier, if any.  If virtual inheritance is used, the base class is referred to as a virtual base class.
 
-Multiple base classes can be specified, separated by commas.  If a single base class is specified, the inheritance model is [Single inheritance](../cpp/single-inheritance.md).If more than one base class is specified, the inheritance model is called [Multiple inheritance](../cpp/multiple-base-classes.md).
+Multiple base classes can be specified, separated by commas.  If a single base class is specified, the inheritance model is [Single inheritance](../cpp/single-inheritance.md). If more than one base class is specified, the inheritance model is called [Multiple inheritance](../cpp/multiple-base-classes.md).
 
 The following topics are included:
 

docs/cppcx/partial-classes-c-cx.md

@@ -42,7 +42,7 @@ The following code fragment demonstrates accessibility. In the first partial cla
 
 A partial definition of a class such as `MyClass` is only a declaration of MyClass. That is, it only introduces the name `MyClass`. `MyClass` can't be used in a way that requires a class definition, for example, knowing the size of `MyClass` or using a base or member of `MyClass`. `MyClass` is considered to be defined only when the compiler encounters a non-partial definition of `MyClass`.
 
-The following example demonstrates the declaration behavior of a partial class. After declaration #1, `MyClass` can be used as if it were written as the forward declaration, `ref class MyClass;`. Declaration #2 is equivalent to declaration #1.Declaration #3 is valid because it's a forward declaration to a class. But declaration #4 is invalid because
+The following example demonstrates the declaration behavior of a partial class. After declaration #1, `MyClass` can be used as if it were written as the forward declaration, `ref class MyClass;`. Declaration #2 is equivalent to declaration #1. Declaration #3 is valid because it's a forward declaration to a class. But declaration #4 is invalid because
 
 `MyClass` is not fully defined.
 

docs/error-messages/compiler-errors-1/compiler-error-c2139.md

@@ -1,17 +1,18 @@
 ---
 description: "Learn more about: Compiler Error C2139"
 title: "Compiler Error C2139"
-ms.date: "11/04/2016"
+ms.date: 05/03/2021
 f1_keywords: ["C2139"]
 helpviewer_keywords: ["C2139"]
-ms.assetid: 31e047c0-5bf9-46c2-b6de-b627ea6a5768
 ---
 # Compiler Error C2139
 
-'type' : an undefined class is not allowed as an argument to compiler intrinsic type trait 'trait'
+> '*type*' : an undefined class is not allowed as an argument to compiler intrinsic type trait '*trait*'
 
 An invalid argument was passed to a type trait.
 
+## Remarks
+
 For more information, see [Compiler Support for Type Traits](../../extensions/compiler-support-for-type-traits-cpp-component-extensions.md).
 
 ## Example

docs/error-messages/compiler-errors-1/compiler-error-c2201.md

@@ -1,18 +1,19 @@
 ---
 description: "Learn more about: Compiler Error C2201"
 title: "Compiler Error C2201"
-ms.date: "11/04/2016"
+ms.date: 05/03/2021
 f1_keywords: ["C2201"]
 helpviewer_keywords: ["C2201"]
-ms.assetid: ed927659-6e9c-447d-9963-19969ae1e957
 ---
 # Compiler Error C2201
 
-'identifier' : must have external linkage in order to be exported/imported
+> '*identifier*' : must have external linkage in order to be exported/imported
 
 The exported identifier is **`static`**.
 
-The following sample generates C2286:
+## Example
+
+The following sample generates C2286, and shows how to fix it:
 
 ```cpp
 // C2201.cpp

docs/error-messages/compiler-errors-2/compiler-error-c2668.md

@@ -1,18 +1,18 @@
 ---
 description: "Learn more about: Compiler Error C2668"
 title: "Compiler Error C2668"
-ms.date: "03/28/2017"
+ms.date: 05/03/2021
 f1_keywords: ["C2668"]
 helpviewer_keywords: ["C2668"]
 ms.assetid: 041e9627-1c76-420e-a653-cfc83f933bd3
 ---
 # Compiler Error C2668
 
-'function' : ambiguous call to overloaded function
+> 'function' : ambiguous call to overloaded function
 
-The specified overloaded function call could not be resolved. You may want to explicitly cast one or more of the actual parameters.
+The specified overloaded function call couldn't be resolved. You may want to explicitly cast one or more of the actual parameters.
 
-You can also get this error through template use. If, in the same class, you have a regular member function and a templated member function with the same signature, the templated one must come first. This is a limitation of the current implementation of Visual C++.
+You can also get this error through template use. If, in the same class, you have a regular member function and a templated member function with the same signature, the templated one must come first. This limitation remains in the current implementation of Visual C++.
 
 ## Examples
 
@@ -34,7 +34,7 @@ int main() {
 }
 ```
 
-Another way to resolve this error is with a [using declaration](../../cpp/using-declaration.md):
+Another way to resolve this error is with a [`using` declaration](../../cpp/using-declaration.md):
 
 ```cpp
 // C2668b.cpp
@@ -75,9 +75,7 @@ class MyTestCase : public AppTestCase {
 };
 ```
 
-This error can also be generated as a result of compiler conformance work that was done for Visual Studio .NET 2003: ambiguous conversion on cast of constant 0.
-
-Conversion on a cast using constant 0 is ambiguous since int requires a conversion both to long and to void*. To resolve this error, cast 0 to the exact type of the function parameter it is being used for so that no conversions need to take place (this code will be valid in the Visual Studio .NET 2003 and Visual Studio .NET versions of Visual C++).
+Conversion on a cast using constant 0 is ambiguous since **`int`** requires a conversion both to **`long`** and to `void*`. To resolve this error, cast 0 to the exact type of the function parameter it's being used for. Then no conversions need to take place.
 
 ```cpp
 // C2668c.cpp
@@ -97,7 +95,7 @@ int main() {
 }
 ```
 
-This error can occur because the CRT now has float and double forms of all math functions.
+This error can occur because the CRT now has **`float`** and **`double`** forms of all math functions.
 
 ```cpp
 // C2668d.cpp
@@ -110,7 +108,7 @@ int main() {
 }
 ```
 
-This error can occur because the pow(int, int) was removed from math.h in the CRT.
+This error can occur because the `pow(int, int)` was removed from *`math.h`* in the CRT.
 
 ```cpp
 // C2668e.cpp
@@ -121,7 +119,7 @@ int main() {
 }
 ```
 
-This code succeeds in Visual Studio 2015 but fails in Visual Studio 2017 and later with C2668. In Visual Studio 2015, the compiler erroneously treated copy-list-initialization in the same way as regular copy-initialization; it considered only converting constructors for overload resolution.
+This code succeeds in Visual Studio 2015 but fails in Visual Studio 2017 and later with C2668. In Visual Studio 2015, the compiler erroneously treated copy-list-initialization in the same way as regular copy-initialization. It considered only converting constructors for overload resolution.
 
 ```cpp
 struct A {

docs/error-messages/compiler-errors-2/compiler-error-c7536.md

@@ -0,0 +1,19 @@
+---
+description: "Learn about the causes of Compiler error C7536 and how to fix it."
+title: "Compiler Error C7536"
+ms.date: 05/03/2021
+f1_keywords: ["C7536"]
+helpviewer_keywords: ["C7536"]
+---
+# Compiler Error C7536
+
+> ifc failed integrity checks.  Expected SHA2: '*hash-value*'
+
+The compiler raises C7536 whenever the *`.ifc`* file has been tampered with. The header of the module interface contains an SHA2 hash of the contents below it. On import, the *`.ifc`* file is hashed, then checked against the hash provided in the header. If these don't match, error C7536 is raised:
+
+```Output
+error C7536: ifc failed integrity checks.
+Expected SHA2: '66d5c8154df0c71d4cab7665bab4a125c7ce5cb9a401a4d8b461b706ddd771c6'
+```
+
+This error is new in Visual Studio 2017 version 15.9. It's only generated when creating or consuming modules, specified by the `/experimental:module` compiler option.