You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking at the NSObject(RACSubscribable) category, and it would seem that all of its methods assert conformance to <RACSubscribable> at runtime. Wouldn't this be better placed in the actual <RACSubscribable> protocol? It seems like that would be the safer and more hygienic approach.
Are there some use-cases that make the current approach necessary, or at least more optimal?
The text was updated successfully, but these errors were encountered:
Those are all just conveniences so you don't have to manually create a RACSubscriber all the time. They're all based off <RACSubscribable> methods but since protocols can't have concrete implementations... we're left to implement them as a category.
I'm looking at the
NSObject(RACSubscribable)
category, and it would seem that all of its methods assert conformance to<RACSubscribable>
at runtime. Wouldn't this be better placed in the actual<RACSubscribable>
protocol? It seems like that would be the safer and more hygienic approach.Are there some use-cases that make the current approach necessary, or at least more optimal?
The text was updated successfully, but these errors were encountered: