Does that mean no KVO, swizzling, etc. on stuff the original author doesn’t want you to observe?
Conversation
Many ObjC properties aren't KVO in practice, but there's no way to express that. I think it's a good choice.
1
it seems a shame to restrict its use only to cases the original API author can think of in advance.
2
would ReactiveCocoa have been possible if KVO only worked for stuff Apple thought we'd need it for?
1
1
1
1
4
Replying to