Conversation
We're not yet using the new Swift 4 Package manifest syntax because the manifest must still be compatible with Swift 3.
We're dropping Swift 3.0 compatibility because Swift 3.0 doesn't understand the `swiftLanguageVersions` key in the Package.swift manifest. The code should still be compatible with Swift 3.0 at this moment. I don't think this is a big deal since moving from Swift 3.0 to Swift 3.1 should be straightforward.
- Use `swift package clean` instead of the deprecated `swift build --clean` - Run Swift Package Manager tests in parallel - Print version and debug information before running - Cleanup
Owner
Author
|
Travis is failing (as usual), but I really don't think there's a problem with a code. Merging this. |
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.
No description provided.