Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Recent State of ReactiveCocoa

Recent State of ReactiveCocoa

関西モバイルアプリ研究会 #13での発表資料です #関モバ

http://kanmoba.connpass.com/event/28416/

Sho Ikeda

April 26, 2016
Tweet

More Decks by Sho Ikeda

Other Decks in Programming

Transcript

  1. Reactive Swift Meetup • ReactiveCocoaೖ໳ by @Nirma • Getting Started

    with ReactiveCocoa v4.1.0 by @inamiy • Carthage and ReactiveCocoa by @ikesyo
  2. Moving Rex to the ReactiveCocoa org #2790 1. Discoverability 2.

    Credibility 3. Expansion 4. Easier to manage
  3. Split Objective-C and Swift APIs going forward #2807 Correct me

    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?
  4. ඇಉظॲཧͷఆܕԽ • ಉظతAPI • ςετɺCLIϓϩάϥϜ • RxSwift: RxBlocking // SignalProducer

    func first() -> Result<Value, Error>? func single() -> Result<Value, Error>? func last() -> Result<Value, Error>? func wait() -> Result<(), Error>
  5. ܕ෇͚͞ΕͨΤϥʔ • Signal<Value, Error>, SignalProducer<Value, Error> • Result<Value, Error> ͔Βͷੜ੒:

    attempt, attemptMap • throwsΛѻ͏࣌͸໌നͳܕ΁ͷΩϟετɺ΋͘͠͸NSErrorͱ ͯ͠ѻ͏ʢResultͷAPIʣ • RAC: Atomic, MutablePropertyΛআ͍ͯthrows͸࢖ΘΕ͍ͯͳ ͍ • Carthage: throws͸࢖ΘΕ͍ͯͳ͍