Skip to content

Commit 9a03419

Browse files
committed
Tweaked the wording of one of the data race safety FAQ points.
1 parent e9c475a commit 9a03419

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

Resources/Markdown/docs/builds.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,6 +92,6 @@ You can [find more details in this issue](https://github.com/SwiftPackageIndex/S
9292

9393
The Swift 6.0 compiler can check whether code is safe from data races at compile time with “complete” concurrency checks enabled. The data race safety information we publish on package pages comes from diagnostics output by the compiler as we build each package.
9494

95-
It’s not possible for us to distinguish between a package that genuinely has no data race safety errors and one where the errors are being suppressed. All we can report on is the number of data race errors reported by the compiler.
95+
It’s not possible to distinguish between a package that genuinely has no data race safety errors and one where the errors are being suppressed in code. The number we display on the page is the number of data race errors that the compiler reports.
9696

9797
Note that this does not affect package compatibility, as shown in the compatibility matrix. A package can be fully compatible with Swift 6.x without enabling strict concurrency checks, provided it is not running in Swift 6 language mode. For more information on opting into Swift 6 language mode, [read the Swift 6 migration guide for more information](https://www.swift.org/migration/documentation/swift-6-concurrency-migration-guide/completechecking).

0 commit comments

Comments
 (0)