Skip to content
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 to support building with Swift 4.2 #37

Merged
merged 3 commits into from
Sep 10, 2018
Merged

Update to support building with Swift 4.2 #37

merged 3 commits into from
Sep 10, 2018

Conversation

keith
Copy link
Contributor

@keith keith commented Sep 10, 2018

This likely shouldn't be merged until Swift 4.2 is officially released (hopefully this week)

@keith
Copy link
Contributor Author

keith commented Sep 10, 2018

CI is failing until Swift 4.2 is released

Package.swift Outdated
@@ -11,5 +11,6 @@ let package = Package(
targets: [
.target(name: "Spectre", dependencies: []),
.testTarget(name: "SpectreTests", dependencies: ["Spectre"]),
]
],
swiftLanguageVersions: [.v4, .v4_2]
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

v4 doesn't include 4.2?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would this break support on 4.0 because it would have no idea about the .4_2 enumeration?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

v4 doesn't include 4.2?

If you don't add 4.2 explicitly SwiftPM will assume 4 only

Would this break support on 4.0 because it would have no idea about the .4_2 enumeration?

It depends on what you mean by 4.0 here. It will require the Swift 4.2 (or newer) compiler, but it can still compile with Swift 4.0 syntax. Alternatively I can create a new [email protected] file, and not touch this one, to support both simultaneously going forward.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated with the new file instead

@keith
Copy link
Contributor Author

keith commented Sep 10, 2018

With this new file this would actually be fine to merge before the official release, if we could get CI to pass

@keith
Copy link
Contributor Author

keith commented Sep 10, 2018

I reverted my CI changes for now

@kylef kylef merged commit 354153b into kylef:master Sep 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants