Snapshots.

Author: daveverwer

Tests/AppTests/__Snapshots__/WebpageSnapshotTests/test_ReadyForSwift6Show.1.html

@@ -78,15 +78,16 @@ <h1>
     <main>
       <div class="inner">
         <h2>Ready for Swift 6</h2>
-        <p>Swift 6 brings with it the ability to check your code for concurrency and data race issues. If switched on, the Swift compiler will produce errors where you could have data races.</p>
-        <p>For help migrating your code, see the 
-          <a href="https://example.com">Swift 6 language mode migration guide</a> or the 
-          <a href="https://example.com">Swift 6 release blog post</a>
-        </p>
+        <p>The Swift 6 language mode prevents data-races at compile time. When you opt into Swift 6 mode, the compiler will produce errors when your code has a risk of concurrent access, turning hard-to-debug runtime failures into compiler errors.</p>
+        <p>To track the progress of the Swift package ecosystem, the Swift Package Index is running regular package compatibility checks across all packages in the index.</p>
         <p>To track the progress of the Swift package ecosystem, the Swift Package Index is running regular package compatibility checks across all packages in the index.</p>
         <h3>Total packages compatible with Swift 6</h3>
+        <p>Packages with zero data-race safety compiler diagnostics during a successful build on at least one tested platform.</p>
         <p>Couldn’t load chart data.</p>
         <h3>Total Swift 6 concurrency errors</h3>
+        <p>The total number of all data-race safety diagnostics across 
+          <em>all</em> packages.
+        </p>
         <p>Couldn’t load chart data.</p>
         <h3>Frequently asked questions</h3>
         <p>
@@ -96,6 +97,27 @@ <h3>Frequently asked questions</h3>
           <strong>A: </strong>We define compatibility in the same way we do on package pages. If any build of the package completes successfully on any of our tested platforms (macOS via SwiftPM, macOS via XcodeBuild, iOS, visionOS, watchOS, tvOS, or Linux) then that build is deemed compatible with the Swift version.
         </p>
         <hr class="minor"/>
+        <p>
+          <strong>Q: </strong>Are additional parameters added to the build command for these tests compared to the “standard” Swift Package Index builds that determine Swift version compatibility on package pages?
+        </p>
+        <p>
+          <strong>A: </strong>Yes. The builds that produce the results on this page have strict concurrency checking set to 
+          <code>complete</code> to check for data race safety in Swift 6 language mode. We pass 
+          <code>-strict-concurrency=complete</code> to either 
+          <code>swift build</code> or 
+          <code>xcodebuild</code>.
+        </p>
+        <hr class="minor"/>
+        <p>
+          <strong>Q: </strong>Why use 
+          <code>-strict-concurrency=complete</code> instead of 
+          <code>-swift-version 6</code>?
+        </p>
+        <p>
+          <strong>A: </strong>Data-race safety diagnostics are determined in different stages of the compiler. For example, type checking produces some data-race safety errors, and others are diagnosed during control-flow analysis after code generation. If type checking produces errors, the compiler will not proceed to code generation, so testing with 
+          <code>-swift-version 6</code> would show fewer errors than really exist across the package ecosystem.
+        </p>
+        <hr class="minor"/>
         <p>
           <strong>Q: </strong>What does “total concurrency errors” mean?
         </p>