(At least according to the docs/undocmented.json file created by jazzy.)
Also attemps to unify the documentation style, fixes typos found in
documentation, and adds some functional tests for PMKJoint.
Having to specialize your thens makes using PromiseKit much less pleasant.
However naming our functions more verbosely, for example:
CLLocationManager.promiseLocations()
// versus
CLLocationManager.promiseLocation()
Read confusingly. This new idea allows promises to be non-ambiguous yet
specialization is easy. For example:
NSURLSession.GET(url).then { data in } // no compiler ambiguity!
// or:
NSURLSession.GET(url).asImage().then { image in }
If you need this, you must write some Swift. The ObjC simply doesn’t work with the Swift 2 beta due to the implicit ErrorType -> NSError conversions and this seems a good enough opportunity to cut this code. Since the function is one-time use per app it seems the inconvenience for an ObjC developer is acceptable.
