To be fair, they hadn't been mentioned in the thread thus far, and in fact hadn't been published by the time of my own feedback: Async Algorithms answers basically half of my feedback items.
2 Likes
For anyone coming now who wants to know whether and how the bug is fixed: I recently retested, and it turns out this was fixed by an OS update in my case. I can't track down when it happened exactly, I just know it is fixed in Monterey 12.4. So no need to watch the version of Swift in Xcode or try and dissect whether Swift 5.6 means 5.6.2 or 5.6.1 or 5.6.0 : it's going to depend on which OS version is going to run your executable anyway (unless you're using the backdeployment feature, in which case you're on your own).
Note that Instruments unconditionally implies that your deliverable includes the libSwift_Concurrency.dylib library, even when you don't use the backdeployment feature. This is demonstrably wrong (FB10689676).
1 Like