mirror of
https://github.com/JohnEstropia/CoreStore.git
synced 2026-01-11 20:00:30 +01:00
Swift 3 #68
Reference in New Issue
Block a user
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 @tosbaha on GitHub (Jul 19, 2016).
Hi,
Thanks for such a great library. I am in the middle of upgrading my Core Data layer and I was searching for library and luckily I found yours. I think your library by far has the best documentation. I forked and tried to upgrade to Swift 3 syntax but after 20 minutes I still couldn't make it build. I will really appreciate if you can create Swift3 branch so that people like me can have more time to test it out before Swift 3 becomes stable. Best regards.
@JohnEstropia commented on GitHub (Jul 20, 2016):
Thanks for the feedback!
I'm working on the Swift 3 conversion right now. It's taking a while because I want to meet the Swift 3 API Design Guideline, but the Swift 3 branch should be ready within a couple weeks :)
@JohnEstropia commented on GitHub (Aug 8, 2016):
To everyone watching this thread, a working library is in the swift3_develop branch.
Do note that due to Swift 3 not yet in it's final stage and me still not satisfied of the Swift-3-ness of some of CoreStore's API naming rules, there's a good chance that it will be refactored once or twice more before the final Swift 3 release.
@JoeMatt commented on GitHub (Aug 10, 2016):
Now that Swift 3 has many (all?) of the GCD features of GCD kit (with almost the same syntax, they must have been inspired) will that library be dropped in favor of the Swift 3 APIs?
How does the introduction of CoreData generations effect CoreStore? Will the new APIs for syncing and such be exposed? Is concurrency less of an issue, it seems they're making it just work?
@JohnEstropia commented on GitHub (Aug 11, 2016):
Yup, I wanted to try migrating to the new dispatch API but the last beta broke my local build so I thought just wait for the final version of the API before I fully commit.
I have no iOS 10 device yet so I haven't tried, but I heard the new SDK changes should "just work". Now knowing iOS SDK updates I doubt that's true, but I'm holding off any actual testing until after Swift 3 is sorted out and the iOS 10 GM build is released.
@JohnEstropia commented on GitHub (Sep 14, 2016):
Just to update, the
swift3_developbranch is fully working right now.GCDKit dependency was also removed and the demo app works fine on iOS 10.
That said, I encourage everyone to wait for the final
masterversion because I am still updating the API to match the Swift 3 API Guidelines. If anyone wants to suggest improvements regarding Swift 3, feel free to comment or make pull requests!@mrichtsfeld commented on GitHub (Nov 28, 2016):
Hi @JohnEstropia
Great framework, love working with it. I have been using with with swift3 now for almost 2 months and it works fine. Do you plan to merge it to master soon?
Thanks
@JohnEstropia commented on GitHub (Nov 28, 2016):
@mrichtsfeld Yes it does work fine :) We use it in our apps as well. I just have a couple more pending refactors before I can finalize the Swift 3 branch.
@mrichtsfeld commented on GitHub (Nov 28, 2016):
@JohnEstropia Looking forward to it. Thanks for the update.
@JohnEstropia commented on GitHub (Jan 7, 2017):
Sorry for the long wait, Swift 3 is now in the master branch and pushed to Cocoapods as version 3.0.0!