Closed danielvera64 closed 1 year ago
Hi @danielvera64! Sorry for the delay in this!
Enabling concurrency checking is a goal for Nimble 13 (as of this writing, Nimble 13 is 2 major versions away). If you're interested, https://github.com/Quick/Nimble/pull/1040 is a draft PR with some very early work on this. At this point, I don't know what I'll be doing about Nimble's usage of DispatchTimeInterval (I'm against making it conform to Sendable in Nimble, so unless Apple makes it & related APIs conform to Sendable, then likely the path is to create our own API for specifying a time interval). This is clearly on my radar.
Again, thanks for raising the priority of enabling concurrency checking for Nimble!
What did you do?
I changed the
SWIFT_STRICT_CONCURRENCY
flag to targeted and now the tests that are annotated as a main actor and usetoEventually
now show the following warning:The warning can be disabled by using the
@preconcurrency
annotation in the Dispatch import but I would prefer not adding that annotation.What did you expect to happen?
Not showing the
DispatchTimeInterval
warning.What actually happened instead?
Shows the following warning
Environment
List the software versions you're using:
Please also mention which package manager you used and its version. Delete the other package managers in this list:
Project that demonstrates the issue