Merge pull request #82088 from bnbarham/missing-doc-files

[Doc] Add missing diagnostic groups

Author: bnbarham

userdocs/diagnostics/diagnostic-descriptions.md

@@ -0,0 +1,37 @@
+# Diagnostic descriptions
+
+Detailed explanations for various compiler diagnostics.
+
+
+## Overview
+
+Swift diagnostics are classified into errors and warnings. Warnings can only be silenced in an
+intentional manner, e.g., adding `_ =` for an unused function result.
+
+Some diagnostics have more detailed explanations available. These include a `[#Name]` inline and
+reference to this documentation at the end of the compiler output on the command line, or is
+presented specially within your IDE of choice. See below for the full list of these notes.
+
+
+## Topics
+
+- <doc:actor-isolated-call>
+- <doc:conformance-isolation>
+- <doc:dynamic-callable-requirements>
+- <doc:error-in-future-swift-version>
+- <doc:existential-member-access-limitations>
+- <doc:isolated-conformances>
+- <doc:multiple-inheritance>
+- <doc:mutable-global-variable>
+- <doc:nominal-types>
+- <doc:opaque-type-inference>
+- <doc:property-wrapper-requirements>
+- <doc:protocol-type-non-conformance>
+- <doc:result-builder-methods>
+- <doc:sendable-closure-captures>
+- <doc:sending-closure-risks-data-race>
+- <doc:sendable-metatypes>
+- <doc:sending-risks-data-race>
+- <doc:string-interpolation-conformance>
+- <doc:temporary-pointers>
+- <doc:trailing-closure-matching>

userdocs/diagnostics/diagnostic-groups.md

@@ -0,0 +1,34 @@
+# Diagnostic groups
+
+Diagnostic groups allow controlling the behavior of warnings in a more precise manner.
+
+
+## Overview
+
+Diagnostic groups collect some number of diagnostics together under a common group name. This allows
+for extra documentation to help explain relevant language concepts, as well as the ability to
+control the behavior of warnings in a more precise manner:
+- `-Werror <group>` - upgrades warnings in the specified group to errors
+- `-Wwarning <group>` - indicates that warnings in the specified group should remain warnings, even
+  if they were previously upgraded to errors
+
+As a concrete example, to upgrade deprecated declaration warnings to errors:
+```sh
+-Werror DeprecatedDeclaration
+```
+
+Or upgrade all warnings except deprecated declaration to errors:
+```sh
+-warnings-as-errors -Wwarning DeprecatedDeclaration
+```
+
+
+## Topics
+
+- <doc:clang-declaration-import>
+- <doc:deprecated-declaration>
+- <doc:preconcurrency-import>
+- <doc:strict-language-features>
+- <doc:strict-memory-safety>
+- <doc:unknown-warning-group>
+

userdocs/diagnostics/upcoming-language-features.md

@@ -0,0 +1,22 @@
+# Upcoming language features
+
+Upcoming language features enable new (but potentially source breaking) functionality that be
+enabled by default in an upcoming language mode.
+
+
+## Overview
+
+Upcoming language features allow the incremental adoption of language features that would otherwise
+only be available in a new language mode, without having to fully migrate to that mode. They can be
+enabled on the command line with `-enable-upcoming-feature <feature>`.
+
+Some upcoming features have an additional "migration" mode, where the compiler will emit warnings
+with fix-its to help migrate to that mode. This can be enabled with `-enable-upcoming-feature
+<feature>:migrate`.
+
+
+## Topics
+
+- <doc:existential-any>
+- <doc:member-import-visibility>
+- <doc:nonisolated-nonsending-by-default>