Enable users to specify their preferred Swift syntax options to facilitate a flexible transition#225
Open
shimastripe wants to merge 1 commit intosindresorhus:mainfrom
Open
Conversation
…itate a flexible transition
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
1 participant
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
HOW
This approach is used in libraries such as pointfree’s; since fixing the Swift syntax version would require updating all dependent libraries at once, this option allows for multiple versions provided there are no breaking changes.
I understand how far back we should support, but wouldn’t it be possible to handle updates more flexibly by supporting the latest version and the previous one?