feat: sync with swift-book

Author: zhangqifan

TSPL.docc/GuidedTour/Compatibility.md

@@ -33,7 +33,7 @@ Concurrency requires the Swift 5 language mode
 and a version of the Swift standard library
 that provides the corresponding concurrency types.
 On Apple platforms, set a deployment target
-of at least iOS 13, macOS 10.15, tvOS 13, or watchOS 6.
+of at least iOS 13, macOS 10.15, tvOS 13, watchOS 6, or visionOS 1.
 
 A target written in Swift 6 can depend on
 a target that's written in Swift 5, Swift 4.2 or Swift 4,

TSPL.docc/LanguageGuide/ControlFlow.md

@@ -2159,7 +2159,7 @@ the body of the `if` executes on the minimum deployment target specified by your
 
 In its general form,
 the availability condition takes a list of platform names and versions.
-You use platform names such as `iOS`, `macOS`, `watchOS`, and `tvOS` ---
+You use platform names such as `iOS`, `macOS`, `watchOS`, `tvOS`, and `visionOS` ---
 for the full list, see <doc:Attributes#Declaration-Attributes>.
 In addition to specifying major version numbers like iOS 8 or macOS 10.10,
 you can specify minor versions numbers like iOS 11.2.6 and macOS 10.13.3.

TSPL.docc/LanguageGuide/ErrorHandling.md

@@ -745,7 +745,7 @@ in the following special cases:
   and propagates any errors from that closure.
   For a comparison between propagating a specific error type
   and using `rethrows`,
-  see <doc:Declarations:Rethrowing-Functions-and-Methods>.
+  see <doc:Declarations#Rethrowing-Functions-and-Methods>.
 
 For example,
 consider code that summarizes ratings

TSPL.docc/LanguageGuide/Macros.md

@@ -274,7 +274,7 @@ public macro OptionSet<RawType>() =
 ```
 
 In the declaration above,
-the `@attached(member)` macro includes arguments after the `named:` label
+the `@attached(member)` macro includes arguments after the `names:` label
 for each of the symbols that the `@OptionSet` macro generates.
 The macro adds declarations for symbols named
 `RawValue`, `rawValue`, and `init` ---

TSPL.docc/ReferenceManual/Attributes.md

@@ -1694,11 +1694,10 @@ The additional result-building methods are as follows:
   or to perform other postprocessing on a result before returning it.
 
 - term `static func buildLimitedAvailability(_ component: Component) -> Component`:
-  Builds a partial result that propagates or erases type information
-  outside a compiler-control statement
+  Builds a partial result that erases type information.
+  You can implement this method to prevent type information
+  from propagating outside a compiler-control statement
   that performs an availability check.
-  You can use this to erase type information
-  that varies between the conditional branches.
 
 For example, the code below defines a simple result builder
 that builds an array of integers.
@@ -1797,9 +1796,14 @@ into code that calls the static methods of the result builder type:
   You can define an overload of `buildExpression(_:)`
   that takes an argument of type `()` to handle assignments specifically.
 - A branch statement that checks an availability condition
-  becomes a call to the `buildLimitedAvailability(_:)` method.
+  becomes a call to the `buildLimitedAvailability(_:)` method,
+  if that method is implemented.
+  If you don't implement `buildLimitedAvailability(_:)`,
+  then branch statements that check availability
+  use the same transformations as other branch statements.
   This transformation happens before the transformation into a call to
   `buildEither(first:)`, `buildEither(second:)`, or `buildOptional(_:)`.
+
   You use the `buildLimitedAvailability(_:)` method to erase type information
   that changes depending on which branch is taken.
   For example,
@@ -1874,7 +1878,7 @@ into code that calls the static methods of the result builder type:
 
   To solve this problem,
   implement a `buildLimitedAvailability(_:)` method
-  to erase type information.
+  to erase type information by returning a type that's always available.
   For example, the code below builds an `AnyDrawable` value
   from its availability check.
 
@@ -1884,7 +1888,7 @@ into code that calls the static methods of the result builder type:
       func draw() -> String { return content.draw() }
   }
   extension DrawingBuilder {
-      static func buildLimitedAvailability(_ content: Drawable) -> AnyDrawable {
+      static func buildLimitedAvailability(_ content: some Drawable) -> AnyDrawable {
           return AnyDrawable(content: content)
       }
   }
@@ -2276,7 +2280,7 @@ into code that calls the static methods of the result builder type:
          func draw() -> String { return content.draw() }
      }
   -> extension DrawingBuilder {
-         static func buildLimitedAvailability(_ content: Drawable) -> AnyDrawable {
+         static func buildLimitedAvailability(_ content: some Drawable) -> AnyDrawable {
              return AnyDrawable(content: content)
          }
      }

TSPL.docc/ReferenceManual/Declarations.md

@@ -3940,14 +3940,21 @@ Access control is discussed in detail in <doc:AccessControl>.
   only by code within the declaration's immediate enclosing scope.
 
 For the purpose of access control,
-extensions to the same type that are in the same file
-share an access-control scope.
-If the type they extend is also in the same file,
-they share the type's access-control scope.
-Private members declared in the type's declaration
-can be accessed from extensions,
-and private members declared in one extension
-can be accessed from other extensions and from the type's declaration.
+extensions behave as follows:
+
+- If there are multiple extensions in the same file,
+  and those extensions all extend the same type,
+  then all of those extensions have the same access-control scope.
+  The extensions and the type they extend can be in different files.
+
+- If there are extensions in the same file as the type they extend,
+  the extensions have the same access-control scope as the type they extend.
+
+- Private members declared in a type's declaration
+  can be accessed from extensions to that type.
+  Private members declared in one extension
+  can be accessed from other extensions
+  and from the extended type's declaration.
 
 Each access-level modifier above optionally accepts a single argument,
 which consists of the `set` keyword enclosed in parentheses ---

TSPL.docc/ReferenceManual/LexicalStructure.md

@@ -260,6 +260,7 @@ so they must be escaped with backticks in that context.
   `inout`,
   `internal`,
   `let`,
+  `nonisolated`,
   `open`,
   `operator`,
   `private`,

TSPL.docc/ReferenceManual/Statements.md

@@ -1253,7 +1253,7 @@ see <doc:Expressions#Explicit-Member-Expression>.
 > *platform-condition* → **`canImport`** **`(`** *import-path* **`)`** \
 > *platform-condition* → **`targetEnvironment`** **`(`** *environment* **`)`**
 >
-> *operating-system* → **`macOS`** | **`iOS`** | **`watchOS`** | **`tvOS`** | **`Linux`** | **`Windows`** \
+> *operating-system* → **`macOS`** | **`iOS`** | **`watchOS`** | **`tvOS`** | **`visionOS`** | **`Linux`** | **`Windows`** \
 > *architecture* → **`i386`** | **`x86_64`** | **`arm`** | **`arm64`** \
 > *swift-version* → *decimal-digits* *swift-version-continuation*_?_ \
 > *swift-version-continuation* → **`.`** *decimal-digits* *swift-version-continuation*_?_ \
@@ -1341,7 +1341,7 @@ The compiler uses the information from the availability condition
 when it verifies that the APIs in that block of code are available.
 
 The availability condition takes a comma-separated list of platform names and versions.
-Use `iOS`, `macOS`, `watchOS`, and `tvOS` for the platform names,
+Use `iOS`, `macOS`, `watchOS`, `tvOS` and `visionOS` for the platform names,
 and include the corresponding version numbers.
 The `*` argument is required and specifies that, on any other platform,
 the body of the code block guarded by the availability condition
@@ -1398,7 +1398,8 @@ It has the same meaning as the `*` argument in an availability condition.
   >>               macOS 1, macOSApplicationExtension 1,
   >>               macCatalyst 1, macCatalystApplicationExtension 1,
   >>               watchOS 1, watchOSApplicationExtension 1,
-  >>               tvOS 1, tvOSApplicationExtension 1, *) {
+  >>               tvOS 1, tvOSApplicationExtension 1,
+  >>               visionOS 1, visionOSApplicationExtension 1, *) {
   >>     print("a")
   >> } else {
   >>     print("b")

TSPL.docc/ReferenceManual/SummaryOfTheGrammar.md

@@ -698,7 +698,7 @@ make the same change here also.
 > *platform-condition* → **`canImport`** **`(`** *import-path* **`)`** \
 > *platform-condition* → **`targetEnvironment`** **`(`** *environment* **`)`**
 >
-> *operating-system* → **`macOS`** | **`iOS`** | **`watchOS`** | **`tvOS`** | **`Linux`** | **`Windows`** \
+> *operating-system* → **`macOS`** | **`iOS`** | **`watchOS`** | **`tvOS`** | **`visionOS`** | **`Linux`** | **`Windows`** \
 > *architecture* → **`i386`** | **`x86_64`** | **`arm`** | **`arm64`** \
 > *swift-version* → *decimal-digits* *swift-version-continuation*_?_ \
 > *swift-version-continuation* → **`.`** *decimal-digits* *swift-version-continuation*_?_ \

TSPL.docc/RevisionHistory/RevisionHistory.md

@@ -2,6 +2,10 @@
 
 Review the recent changes to this book.
 
+**XXX release date XXX**
+
+- Minor corrections throughout.
+
 **2024-06-10**
 
 - Updated for Swift 6.

TSPL.docc/The-Swift-Programming-Language.md

@@ -1,4 +1,4 @@
-# The Swift Programming Language (6.0 beta)
+# The Swift Programming Language (6 beta)
 
 @Metadata {
   @TechnologyRoot