Skip to content

Conversation

daveverwer
Copy link
Member

Screenshot 2024-12-24 at 10 58 17@2x

@finestructure
Copy link
Member

Good idea!

@daveverwer daveverwer merged commit b191f55 into main Dec 24, 2024
6 checks passed
@daveverwer daveverwer deleted the data-race-safety-inconsistencies branch December 24, 2024 14:55

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).

**Note:** If you see inconsistencies between the number of data race safety errors reported by the Swift Package Index and the number you see in local testing, we are [tracking a potential issue with false negatives reported by the Swift compiler](https://github.com/SwiftPackageIndex/SwiftPackageIndex-Server/issues/3233#issuecomment-2560966121). Please feel free to note packages that may be affected in that issue thread.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I kinda wonder if I false positives is the better term here. It depends on which way you're looking at it but I suppose most people would think of the "positive case" as the one where there are errors. When I named the issue I was thinking in terms of positive/negative results and flipped the meaning essentially.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants