Retain object over -setValue:forKeyPath:
Conditionally use a weak reference in -setKeyPath:onObject:

But only if the object's class does not override -allowWeakReference. If
-allowWeakReference is overridden, take that as the canary in the coal mine and
don't use a weak reference.
Xcode 5.1
Revert "Conditionally use a weak reference in -setKeyPath:onObject:"

This reverts commit 2bc6eff66836294480f36c980dd55b18a401cab7.
Merge pull request #1192 from ReactiveCocoa/xcode-5.1-project-changes

Xcode 5.1
Add a workspace for standalone development.
Pull the dependencies from the .xcworkspace.
Hook up the iOS tests too.
Add __strong for explicitness and defensisveness
Comment on objc_precise_lifetime attribute use
Test object lifetime for -setKeyPath:onObject:

This included test will fail prior to c0013d4.

The use of sleep and delayed async doesn't seem ideal, but an implementation
using locks was intermitently crashing because it made retain of the implicit
unsafe_unretained more likely.
Scheme version bump.
Mr. Clean, right behind you
Another scheme to bump.
Document thread-unsafeness of -setKeyPath:onObject:
Bump specta.
Reword comment for clarity?
Merge pull request #1184 from ReactiveCocoa/retain-for-setKeyPathonObject

Retain object over -setValue:forKeyPath:
Make the formatting of private headers more consistent.
Well now I'm just being pedantic.