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

swift 4 changes #27

Closed
wants to merge 2 commits into from
Closed

swift 4 changes #27

wants to merge 2 commits into from

Conversation

ghost
Copy link

@ghost ghost commented Jun 12, 2017

I'm guessing we should tag the merge with a version of 0.8.0, ¿yeah?

@ghost
Copy link
Author

ghost commented Jun 12, 2017

looks like swiftenv isn't ready for Swift 4 yet

We don't have build instructions for 4.0.
The command "eval "$(curl -sL https://gist.githubusercontent.com/kylef/5c0475ff02b7c7671d2a/raw/9f442512a46d7a2af7b850d65a7e9bd31edfb09b/swiftenv-install.sh)"" failed and exited with 1 during .

@ghost ghost mentioned this pull request Jun 12, 2017
@kylef
Copy link
Owner

kylef commented Jun 12, 2017

looks like swiftenv isn't ready for Swift 4 yet

Well, Swift 4 isn't out yet... Perhaps you meant to use a dev snapshot 4.0 such as 4.0-DEVELOPMENT-SNAPSHOT-2017-06-07-a?

@ghost
Copy link
Author

ghost commented Jun 13, 2017

yes indeed, i was in some weird state where 4.0 was a valid version locally, i don't know how that happened but i later ran into the same issue as the CI and resolved it by doing just that.

@ghost
Copy link
Author

ghost commented Jun 13, 2017

passes now 😄

@ghost
Copy link
Author

ghost commented Jun 13, 2017

This should probably not merge into master until 4.0 is nailed down, ¿will you make a swift-4 branch so I can make a PR to that instead?

@pepicrft pepicrft mentioned this pull request Jul 18, 2017
@kylef
Copy link
Owner

kylef commented Aug 4, 2017

Hi @CalQL8ed-K-OS I was wondering if it is possible to make the code compatible with both versions of Swift (3.1.1 and 4 Snapshot). That way we can mere this into master so a release of Spectre will work with both.

@ehyche
Copy link

ehyche commented Sep 14, 2017

@kylef : any update on getting this PR merged?

@kylef
Copy link
Owner

kylef commented Sep 15, 2017

@ehyche Once my feedback (#27 (comment)) is addressed I'll merge this.

@ehyche
Copy link

ehyche commented Sep 15, 2017

@kylef : I am not sure about the changes in .swift-version, but in my PR that I closed I made essentially the same changes and I verified that they worked on both Xcode 8 (Swift 3.2) and Xcode 9 (Swift 4).

@Bersaelor
Copy link

Bersaelor commented Sep 22, 2017

@ehyche @kylef
For SwiftPM you could tag versions on different branches with 0.8.0 vs 0.8.0@swift-4.

(or have a 0.8.0@swift-3 on a legacy swift3.1 branch and the 0.8.0 for Swift-4 on main master)

Looking forward to have the swift4 version of your amazing project :)
(Less warnings in my Kitura-App!)

@kylef
Copy link
Owner

kylef commented Sep 27, 2017

Merged this in 0fd38db

@kylef kylef closed this Sep 27, 2017
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.

None yet

4 participants