-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sendable #70
Comments
let withStrictConcurrency = SwiftSetting.unsafeFlags([
"-Xfrontend", "-strict-concurrency=complete",
"-Xfrontend", "-warn-concurrency",
"-Xfrontend", "-enable-actor-data-race-checks"]) |
I added the constraint to ANKBinaryInteger to keep the noise down. I may reconsider it in the future, but I doubt it will be necessary. I also added Sendable conformances to: ANKError, ANKSign and ANKSigned. |
Hm. ANKBinaryInteger.Words and ANKBitPatternConvertible.BitPattern should be Sendable. |
oscbyspro
added a commit
that referenced
this issue
Apr 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ANKFullWidth and ANKSigned should conform to Sendable. I kind of assumed they already did because they are frozen structs with Sendable properties ...oh, wait, their properties are generic and lack a Sendable constraint. Well, that's a bit of an oversight, but easily fixed. My main consideration is whether I should require all ANKBinaryInteger(s) to be Sendable. Is there an integer model that shouldn't be Sendable?
The text was updated successfully, but these errors were encountered: