[SPARK-56857] Upgrade Swift to 6.3.2#367
Draft
dongjoon-hyun wants to merge 1 commit into
Draft
Conversation
viirya
approved these changes
May 13, 2026
Member
Author
|
I'm waiting for the update of |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR aims to use
Swift 6.3.2instead ofSwift 6.3.1.Why are the changes needed?
To pick up Swift 6.3.2 (2026-05-11), 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:
async letstack 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, #88254).stripConcurrencyto avoid dropping parameter isolation".hop_to_executorremoval" and "Prevent function signature optimization from removing implicit leading isolation parameter".struct_extractfor multi-field structs".Full commit range: 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)