Aron Cedercrantz

With that Apple refers to the object returned by `+[NSUbiquitousKeyValueStore defaultStore]`. This means that you must/should do the following when registering for the `NSUbiquitousKeyValueStoreDidChangeExternallyNotification` notification: ``` objective-c NSUbiquitousKeyValueStore *store =...

I very much like this idea! The `asConnectable` thing has bothered me ever so slightly 😸

I missed reviewing this one I think. I’m personally in favor of this approach and eventually removing the `Connectable` variant.

@cerihughes I’m in favor of the changes made in this PR. Unless we explicitly want to check that two objects are the same instance we should use `XCTAssertEqualObjects(obj1, obj2, desc,...

@marmelroy @cerihughes With Swift 4 it’ll be possible to expose and use types as `UIViewController`. So “all” will be good in about 6 months time.

@marmelroy Thank you for the links and update, much appreciated! From reading the Alamofire discussions I think we should probably go with multiple targets. Like you’ve done in this PR.

@mumme @marmelroy I prefer this solution a lot to what Hub framework does and what was added in #283! Seems like a better way to do it.

There’s a build flag for whether Xcode should link Foundation implicitly: > When linking a target using Objective-C code, implicitly link in Foundation (and if deploying back to an older...