5/13/2022 AM Publish (#4281)

* Fix issues in valarray content

* Acrolinx pass

* Update scanf %c to mention field width

As part of UCRT refactoring, we introduced an undocumented breaking change that follows the C standard that changed out %c specifier from following the usual rules for field width to using the standardized exception for the %c specifier. We should document it.

* Broken link fixed

* Broken link fixed

* Update dynamicbase.md

arm32 and arm64 is not supported for this linker switch as ASLR cannot be disabled for these architectures.

* update code examples

* offer an alternative project type

* fix for github #3859

* acrolinx

* Clarify per Russ' comments

Also update date and add formatting to current standard.

* Work in progress for 17.2 release

* Followup cpp-docs 3871 in linker opts

* Fix grammar and formatting issues

* Update latest-supported-vc-redist.md

In the line 35, at the very end removed an extra dot.

* Fix alarming bidi description

* text tweaks

* bug fix: 1536384 note implicit compiler flag that is set when using header units. Also, update how null is specified.

* fix flag casing

* Address cpp-docs 3857 3865 3877 3882

* simplify code example-related to github #3847 (#4272)

* simplify code example-related to github #3847

* right justify output

* Update docs/c-runtime-library/reference/getdiskfree.md

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

* address feedback

* Recreate Lauren's /TIME update

* fix for github 3787

* Fix formatting.

* acrolinx pass

* more acrolinx

* tech feedback

* Tweak issue templates

* Add two new templates for new doc work

Templates for doc work for new standards conformance in the compiler and tools.

* Fix merge issues

* Fix typo

* Updated per comments

Co-authored-by: [email protected] <[email protected]>
Co-authored-by: Steve Wishnousky <[email protected]>
Co-authored-by: opbld17 <[email protected]>
Co-authored-by: Pritam Ovhal <[email protected]>
Co-authored-by: Lauren Prinn <[email protected]>
Co-authored-by: PRMerger16 <[email protected]>
Co-authored-by: TylerMSFT <[email protected]>
Co-authored-by: PRMerger4 <[email protected]>
Co-authored-by: Tamara K <[email protected]>
Co-authored-by: Matin Sasanpour <[email protected]>
Co-authored-by: Courtney Wales <[email protected]>
Co-authored-by: opbld15 <[email protected]>
Co-authored-by: Dennis Rea <[email protected]>
Co-authored-by: Colin Cooper <[email protected]>
Co-authored-by: Carolyn McSharry <[email protected]>
Co-authored-by: PRMerger12 <[email protected]>
Co-authored-by: Tyler Whitney <[email protected]>
Co-authored-by: Shannon Leavitt <[email protected]>
Co-authored-by: Anna Huff <[email protected]>
Co-authored-by: PRMerger3 <[email protected]>

Author: 21 people

.github/ISSUE_TEMPLATE/new-c---2017-stl-library-documentation-topic-.md

@@ -1,11 +1,13 @@
 ---
-name: 'New C++ 2017 STL library documentation topic '
+name: 'New C++ 2017 STL library documentation topic'
 about: Create a C++ 2017 doc tracking work item
 title: ''
 labels: C++17, STL doc work
 assignees: ''
-
 ---
+{Use this template to request **new** documentation to cover a feature area in the ISO C++17 standard library. Replace this text in curly braces with a description of the feature area to cover. Include a link to the proposal paper that introduced the issue (for example, `[N4086 Removing Trigraphs??!](https://wg21.link/n4086)`), or cite the chapter and section number or \[short.name] in the C++ standard that describes the feature. Add the Visual Studio version that first implements this feature. If you don't know or don't have these values, then this issue template probably isn't the right one to use.
+
+If documentation already exists on docs.microsoft.com for this feature area, and you're requesting an update, bug fix, or clarification, don't use this template. Go to the article on docs.microsoft.com and use the **This page** button in the **Feedback** section at the bottom of the document to create a GitHub issue. Include a citation for the ISO standard feature area in your description.}
 
-ISO paper for this feature: [PaperID]()
-First implemented in: VS 20YY major.minor
+ISO paper or location in the standard for this feature: {insert link or section here}
+First implemented in: {VS 20YY major.minor}

.github/ISSUE_TEMPLATE/new-c---2020-stl-library-documentation-topic-.md

@@ -1,11 +1,13 @@
 ---
-name: 'New C++ 2020 STL library documentation topic '
+name: 'New C++ 2020 STL library documentation topic'
 about: Create a C++ 2020 doc tracking work item
 title: ''
 labels: C++20, STL doc work
 assignees: ''
-
 ---
+{Use this template to request **new** documentation to cover a feature area in the ISO C++20 standard library. Replace this text in curly braces with a description of the feature area to cover. Include a link to the proposal paper that introduced the issue (for example, `[N4086 Removing Trigraphs??!](https://wg21.link/n4086)`), or cite the chapter and section number or \[short.name] in the C++ standard that describes the feature. Add the Visual Studio version that first implements this feature. If you don't know or don't have these values, then this issue template probably isn't the right one to use.
+
+If documentation already exists on docs.microsoft.com for this feature area, and you're requesting an update, bug fix, or clarification, don't use this template. Go to the article on docs.microsoft.com and use the **This page** button in the **Feedback** section at the bottom of the document to create a GitHub issue. Include a citation for the ISO standard feature area in your description.}
 
-ISO paper for this feature: [PaperID]()
-First implemented in: VS 20YY major.minor
+ISO paper or location in the standard for this feature: {insert link or section here}
+First implemented in: {VS 20YY major.minor}

.github/ISSUE_TEMPLATE/new-c---2023-stl-library-documentation-topic.md

@@ -1,11 +1,13 @@
 ---
-name: New C++ 2023 STL library documentation topic
+name: 'New C++ 2023 STL library documentation topic'
 about: Create an issue to track C++ 2023 STL doc work
 title: ''
-labels: C++23
+labels: C++23, STL doc work
 assignees: ''
-
 ---
+{Use this template to request **new** documentation to cover a feature area proposed for the ISO C++23 standard library. Replace this text in curly braces with a description of the feature area to cover. Include a link to the proposal paper that introduced the issue (for example, `[N4086 Removing Trigraphs??!](https://wg21.link/n4086)`), or cite the chapter and section number or \[short.name] in the C++ standard that describes the feature. Add the Visual Studio version that first implements this feature. If you don't know or don't have these values, then this issue template probably isn't the right one to use.
+
+If documentation already exists on docs.microsoft.com for this feature area, and you're requesting an update, bug fix, or clarification, don't use this template. Go to the article on docs.microsoft.com and use the **This page** button in the **Feedback** section at the bottom of the document to create a GitHub issue. Include a citation for the ISO standard feature area in your description.}
 
-ISO paper for this feature: [PaperID](http link to iso paper)
-First implemented in: VS 20YY major.minor
+ISO paper or location in the standard for this feature: {insert link or section here}
+First implemented in: {VS 20YY major.minor}

.github/ISSUE_TEMPLATE/new-c---stl-library-doc-topic-.md

@@ -1,11 +1,13 @@
 ---
-name: 'New C++ STL library documentation topic '
+name: 'New C++ STL library documentation topic'
 about: Create a C++ doc tracking work item
 title: ''
 labels: STL doc work
 assignees: ''
-
 ---
+{Use this template to request **new** documentation to cover a feature area in the ISO C++ standard library. Replace this text in curly braces with a description of the feature area to cover. Include a link to the tracking issue or PR in the [Microsoft/STL](https://github.com/microsoft/STL/pulls) repo that implements the feature area. If relevant, include a link to the proposal paper that introduced the issue (for example, `[N4086 Removing Trigraphs??!](https://wg21.link/n4086)`), or cite the chapter and section number or \[short.name] in the C++ standard that describes the feature. Add the Visual Studio version that first implements this feature. If you don't know or don't have these values, then this issue template probably isn't the right one to use.
+
+If documentation already exists on docs.microsoft.com for this feature area, and you're requesting an update, bug fix, or clarification, don't use this template. Go to the article on docs.microsoft.com and use the **This page** button in the **Feedback** section at the bottom of the document to create a GitHub issue. If possible, include a citation for the ISO standard feature area in your description.}
 
-ISO paper for this feature: [PaperID]()
-First implemented in: VS YYYY major.minor
+[Microsoft/STL](https://github.com/microsoft/STL/pulls) PR, ISO paper or location in the standard for this feature: {insert link or section here}
+First implemented in: {VS 20YY major.minor}

.github/ISSUE_TEMPLATE/new-c--20-compiler-doc-topic.md

@@ -0,0 +1,14 @@
+---
+name: 'New C++20 compiler documentation topic'
+about: Create a C++ doc tracking work item
+title: ''
+labels: C++20, Standard doc work
+assignees: ''
+---
+{Use this template to request **new** documentation to cover a compiler feature area in the ISO C++20 standard. Replace this text in curly braces with a description of the feature area to cover. Include a link to the proposal paper that introduced the issue (for example, `[N4086 Removing Trigraphs??!](https://wg21.link/n4086)`), or cite the chapter and section number or \[short.name] in the C++ standard that describes the feature. Add the Visual Studio version that first implements this feature. If you don't know or don't have these values, then this issue template probably isn't the right one to use.
+
+If documentation already exists on docs.microsoft.com for this feature area, and you're requesting an update, bug fix, or clarification, don't use this template. Go to the article on docs.microsoft.com and use the **This page** button in the **Feedback** section at the bottom of the document to create a GitHub issue. If possible, include a citation for the ISO standard feature area in your description.}
+
+ISO paper or location in the standard for this feature: {insert link or section here}
+
+First implemented in: {VS 20YY major.minor}

.github/ISSUE_TEMPLATE/new-c--23-compiler-doc-topic.md

@@ -0,0 +1,14 @@
+---
+name: 'New C++23 compiler documentation topic'
+about: Create a C++ doc tracking work item
+title: ''
+labels: C++23, Standard doc work
+assignees: ''
+---
+{Use this template to request **new** documentation to cover a compiler feature area in the ISO C++23 standard. Replace this text in curly braces with a description of the feature area to cover. Include a link to the proposal paper that introduced the issue (for example, `[N4086 Removing Trigraphs??!](https://wg21.link/n4086)`), or cite the chapter and section number or \[short.name] in the C++ standard that describes the feature. Add the Visual Studio version that first implements this feature. If you don't know or don't have these values, then this issue template probably isn't the right one to use.
+
+If documentation already exists on docs.microsoft.com for this feature area, and you're requesting an update, bug fix, or clarification, don't use this template. Go to the article on docs.microsoft.com and use the **This page** button in the **Feedback** section at the bottom of the document to create a GitHub issue. If possible, include a citation for the ISO standard feature area in your description.}
+
+ISO paper or location in the standard for this feature: {insert link or section here}
+
+First implemented in: {VS 20YY major.minor}