mirror of
https://github.com/OAuthSwift/OAuthSwift.git
synced 2026-04-26 20:55:57 +03:00
[GH-ISSUE #263] Swift 2.3 Support #154
Labels
No labels
bug
cocoapod
duplicate
enhancement
feature-request
help wanted
help wanted
invalid
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/OAuthSwift#154
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cpinski on GitHub (Aug 9, 2016).
Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/263
Could a Swift 2.3 branch be opened so that I can open a PR with full swift 2.3 support? I am currently on a project that would benefit greatly from having a dedicated Swift 2.3 branch.
@phimage commented on GitHub (Aug 10, 2016):
Since #239 I have not updated xcode beta
There is other change ? Warnings or errors? If yes could be fixed or not using same method from #239
@cpinski commented on GitHub (Aug 10, 2016):
There have been some modifications to the code which makes the diff a little different currently. Also I have updated the project settings to use the project settings recommended by Xcode. I believe the biggest change there is setting SWIFT_OPTIMIZATION_LEVEL = "-Owholemodule". This should speed up the execution of the code.
@cpinski commented on GitHub (Aug 10, 2016):
@phimage I added you as a collaborator on my fork so you can see the changes here
@phimage commented on GitHub (Aug 10, 2016):
ok I simulate a PR and see the change
It's essentially xcode project file change.
So it's for compilation with carthage or xcode (cocoapod is not affected)
The other change seems to be conflict with new code
I will create a swift 2.3 branch
But If you PR I want to see only one commit with only project file change (refork or rebase current branch to a new branch in your fork, make the change and commit)
Thanks in advance
@phimage commented on GitHub (Aug 12, 2016):
fixed by #264