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
One of the consequences of Apple's unfortunate (and usually unnecessary) use of informal protocols is that under UIKit, the NSObject(UIResponderStandardEditActions) category pollutes nearly the entire object namespace with methods like -select:.
The result is that the compiler can't resolve the static type of a -select: message: is it (id → id) → RACSubscribable* or is it id → void? So we get a compiler warning.
This can be solved by renaming RAC's -select: method; with my background, I'd of course suggest -map:, but that would be somewhat non-conformant with the LINQ-inspired scheme you guys have going (as well as the Smalltalk heritage of Objective-C)...
The text was updated successfully, but these errors were encountered:
Incidentally, the way to reproduce the compiler error is to try writing a category on RACSubscribable and send -select: to self, or try sending -select: to an object statically typed id.
One of the consequences of Apple's unfortunate (and usually unnecessary) use of informal protocols is that under UIKit, the
NSObject(UIResponderStandardEditActions)
category pollutes nearly the entire object namespace with methods like-select:
.The result is that the compiler can't resolve the static type of a
-select:
message: is it(id → id) → RACSubscribable*
or is itid → void
? So we get a compiler warning.This can be solved by renaming RAC's
-select:
method; with my background, I'd of course suggest-map:
, but that would be somewhat non-conformant with the LINQ-inspired scheme you guys have going (as well as the Smalltalk heritage of Objective-C)...The text was updated successfully, but these errors were encountered: