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 Charts for Swift 5 compiler #3899

Closed
wants to merge 1 commit into from
Closed

Update Charts for Swift 5 compiler #3899

wants to merge 1 commit into from

Conversation

alanzeino
Copy link

Goals ⚽

Swift 5 compiler warnings

@liuxuan30
Copy link
Member

there is already #3874

@alanzeino
Copy link
Author

there is already #3874

#3874 is not backwards compatible with Swift 4.2. I think my change is the correct one and should be merged.

@liuxuan30
Copy link
Member

liuxuan30 commented Mar 19, 2019

@alanzeino thanks for pointing out the difference, I think @jjatie could work with you to address your issues in that PR. I'm ok to either reopen yours and close #3874.

@alanzeino
Copy link
Author

alanzeino commented Mar 19, 2019

@alanzeino thanks for pointing out the difference, I think @jjatie could work with you to address your issues in that PR. I'm ok to either reopen yours and close #3874.

I'll wait for @jjatie to comment, but this PR is thorough and complete and can be merged now. I also have another change to include in this PR but can't right now as it is closed.

@liuxuan30
Copy link
Member

@jjatie what you think?
@alanzeino he may be busy with this work. so let's wait.

@jjatie
Copy link
Collaborator

jjatie commented Mar 20, 2019

I don't see any reason to have this merged now. Swift 5 is not out yet, and we have yet to support previous versions of Swift through availability checks. Until module stability is locked in for Apple platforms, there isn't a strong reason to either.

@alanzeino
Copy link
Author

I don't see any reason to have this merged now. Swift 5 is not out yet, and we have yet to support previous versions of Swift through availability checks. Until module stability is locked in for Apple platforms, there isn't a strong reason to either.

@jjatie Swift 5 and Xcode 10.2 are about a week or two away but if you want to wait that’s fine.

Sent with GitHawk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants