Support Swift 5 #170
Merged
Support Swift 5 #170
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
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.
Update to Swift 5, and use official Docker images for CI.
Resolves Swift 5 compiler warnings relating to changes to
Data.withUnsafeBytes, for which I haven't been able to track down the relevant Swift Evolution proposal, but there's discussion of here: https://forums.swift.org/t/unsaferawbufferpointer-in-swift-5/22165Also adds JAZZY_ELIGIBLE to one of the Mac builds, so that we can regenerate API docs via the CI, and making the Travis configuration consistent with other IBM-Swift repos.