dongjoon-hyun opened a new pull request, #367: URL: https://github.com/apache/spark-connect-swift/pull/367
### What changes were proposed in this pull request? This PR aims to use `Swift 6.3.2` instead of `Swift 6.3.1`. ### Why are the changes needed? To pick up [Swift 6.3.2 (2026-05-11)](https://github.com/swiftlang/swift/releases/tag/swift-6.3.2-RELEASE), which contains 91 commits on top of 6.3.1, with a heavy focus on concurrency and stack-nesting correctness — directly relevant to this async-heavy project. Notable fixes include: - Follow-up SIL/IRGen work hardening `async let` stack allocation (e.g. *"Fix a bug involving two async lets on the stack at once"*, *"Don't delay stack deallocation of non-nested allocations"*), continuing the line of fixes started in 6.3.1 ([swiftlang/swift#87896](https://github.com/swiftlang/swift/pull/87896), [#88254](https://github.com/swiftlang/swift/pull/88254)). - *"[Concurrency] Fix `stripConcurrency` to avoid dropping parameter isolation"*. - *"[SILOptimizer] fix an erroneous `hop_to_executor` removal"* and *"Prevent function signature optimization from removing implicit leading isolation parameter"*. - *"[IRGen] Sign protocol witnesses in relative witness table access"* / ptrauth discriminator cache fix ([#88105](https://github.com/swiftlang/swift/pull/88105), [#88135](https://github.com/swiftlang/swift/pull/88135)). - *"COWOpts: Don't look through `struct_extract` for multi-field structs"*. Full commit range: [swift-6.3.1-RELEASE...swift-6.3.2-RELEASE](https://github.com/swiftlang/swift/compare/swift-6.3.1-RELEASE...swift-6.3.2-RELEASE). ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Opus 4.7 (1M context) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
