Andy Bartholomew
Andy Bartholomew
Why not have a standardized order for property types?
Here's the full command line output when running `swift test` ``` SwiftTestingCrashResult ()$ swift test --xunit-output xunit.xml --parallel Building for debugging... [2/2] Write swift-version-5BDAB9E9C0126B9D.txt Build complete! (0.12s) error: Exited with...
Verified that this also repros with Xcode 16.3 ``` SwiftTestingCrashResult ()$ swift --version; uname -a swift-driver version: 1.120.5 Apple Swift version 6.1 (swiftlang-6.1.0.110.21 clang-1700.0.13.3) Target: arm64-apple-macosx15.0 Darwin Andys-MacBook-Pro.local 24.3.0 Darwin...
I noticed that with Xcode 16 beta 3 this protocol has been updated: ```swift optional func webView( _ webView: WKWebView, decidePolicyFor navigationAction: WKNavigationAction, decisionHandler: @escaping @MainActor @Sendable (WKNavigationActionPolicy) -> Void...
I verified that these two warnings still occur in Xcode 16 beta 3, although it still goes away with just the `@MainActor` attribute and without the `@Sendable` attribute
Actually we've been using `@preconcurrency` with Xcode 15 already. I think the problem with adding `@MainActor` is that changes the type signature for your delegate method, which is different between...