-
Notifications
You must be signed in to change notification settings - Fork 640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update minimum supported Swift version to Swift 5.7 #1837
Draft
calda
wants to merge
52
commits into
nicklockwood:develop
Choose a base branch
from
calda:cal--update-minimum-swift-version
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Update minimum supported Swift version to Swift 5.7 #1837
calda
wants to merge
52
commits into
nicklockwood:develop
from
calda:cal--update-minimum-swift-version
Conversation
This file contains 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
…ase it's too long or multiline
…erty has optional type
…e property's type is an existential, or if the RHS value has an infix operator
…ivate declarations (nicklockwood#1750) Co-authored-by: Cal Stephens <[email protected]>
…s after MARK comments (nicklockwood#1770)
…secutive groups of properties (nicklockwood#1795)
nicklockwood
force-pushed
the
develop
branch
4 times, most recently
from
September 28, 2024 15:35
58f84c6
to
be3df7b
Compare
nicklockwood
force-pushed
the
develop
branch
9 times, most recently
from
October 8, 2024 18:15
72f5313
to
9f26dd8
Compare
nicklockwood
force-pushed
the
develop
branch
15 times, most recently
from
November 3, 2024 13:21
f8dd14e
to
4414188
Compare
nicklockwood
force-pushed
the
develop
branch
2 times, most recently
from
November 9, 2024 15:49
63ff732
to
43463b5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Based on the current set of CI jobs, SwiftFormat currently supports a minimum Swift version of Swift 5.2, which was released in Feb 2020.
In #1832, we had been talking about using multiple-trailing-closure syntax for a new feature. Multiple trailing closures were introduced in Swift 5.3, so to use this approach we have to update the minimum supported Swift version.
@nicklockwood, what are your general thoughts on what Swift versions should be supported by SwiftFormat?
We could just update to Swift 5.3+, which would lets us use trailing closures. I personally like the sound of Swift 5.7, since it adds a lot of extra functionality that we're missing in Swift 5.2 while still being somewhat older (released in September 2022).