if I'm wrong, but maintaining both an Objective-C and Swift API for RAC is a bit of a burden, right? Perhaps going forward it's worth thinking about slimming ReactiveCocoa down to just support Swift. I'm sure you guys feel the pull of writing things in Swift as much as I do ! Obviously there's a lot of people reliant on the Objective-C APIs (myself included, for some rather large projects) but if there's support for this idea, splitting the language support up into separate repos/projects might be a good first step? What do you think?
move the Objective-C APIs to a separate repo and also move the Obj-C/Swift bridging to a separate repo. This will need to happen as part of the 5.0 release because it is a breaking change.
ReactiveCocoa Community Projects • Inspired by the RxSwift Community • Let's expand the ecosystem! • Slack channel: #reactivecocoa • https://reactivex.slack.com/ • Contact to @ReactiveCocoa if you want to join!
Failed to check out a repository. case RepositoryCheckoutFailed(workingDirectoryURL: NSURL, reason: String, underlyingError: NSError?) /// Failed to read a file or directory at the given URL. case ReadFailed(NSURL, NSError?) /// Failed to write a file or directory at the given URL. case WriteFailed(NSURL, NSError?) ... /// A request to the GitHub API failed. case GitHubAPIRequestFailed(Client.Error) /// An error occurred while shelling out. case TaskError(ReactiveTask.TaskError) }
· ReactiveCocoa/ReactiveCocoa • ReactiveCocoa for a better world • [ON HOLD] ReactiveCocoa 3.0 by jspahrsummers · Pull Request #966 · ReactiveCocoa/ReactiveCocoa • jspahrsummers/RxSwift: Proof-of-concept for implementing Rx primitives in Swift • Release v3.0 · ReactiveCocoa/ReactiveCocoa • Release v4.0 · ReactiveCocoa/ReactiveCocoa • γϯϓϧͳύοέʔδཧπʔϧ Carthage - Realm is a mobile database: a replacement for SQLite & Core Data • The introduction to Reactive Programming you've been missing • ʲ༁ʳ͋ͳ͕ͨٻΊ͍ͯͨϦΞΫςΟϒϓϩάϥϛϯάೖ • RxͷHotͱColdʹ͍ͭͯ - Qiita