Open sharplet opened 7 years ago
Comment by Pierre Habouzit (JIRA)
Controlling the queue to execute work on is a misfeature of dispatch_apply(), there are almost no valid use for it, which is why it was never made available to swift, and there's no plan to change this at this time.
We should fix the diagnostics so that dispatch_apply() redirects to concurrentPErform.
Comment by Kim Topley (JIRA)
Filed [rdar://problem/34162804] for this.
It looks like this was fixed in apple/swift#11777 for the SDK overlay.
Does the Private.swift file in swift-corelibs-libdispatch also need to be updated?
Environment
Apple Swift version 3.1 (swiftlang-802.0.53 clang-802.0.42) Target: x86_64-apple-macosx10.9Additional Detail from JIRA
| | | |------------------|-----------------| |Votes | 0 | |Component/s | libdispatch | |Labels | Improvement | |Assignee | ktopley-apple (JIRA) | |Priority | Medium | md5: 2bebab35e0011d92df8ef134f2df0ba5Issue Description:
The diagnostics for the imported version of
dispatch_apply(3)
are contradictory:The
DispatchQueue.concurrentPerform()
API provides an alternative, but doesn't allow controlling the queue that work will be executed on.