Perhaps to discourage access to the state which isn't respectful of it's changing nature?

> On Aug 6, 2013, at 8:46 AM, Josh Abernathy <notifications@github.com> wrote:
> 
> In ReactiveCocoaFramework/ReactiveCocoa/RACCommand.h:
> 
> >  //
> > -// This property is KVO-compliant, and must only be read from the main thread.
> > -@property (nonatomic, assign, readonly) BOOL canExecute;
> > +// This signal will immediately send YES or NO upon subscription.
> > +@property (nonatomic, strong, readonly) RACSignal *executing;
> I'm curious about the choice of changing this (and the previously non-signal properties) to a RACSignal. Their behavior of starting with the current value is equivalent to observing a non-signal property, and with a property we'd get the type information.
> 
> —
> Reply to this email directly or view it on GitHub.