On Aug 9, 2014, at 18:13 , Roland King <r...@rols.org> wrote: > If this is where we are then it would be handy to have the runtime throw, or > at least log, if you attempt to KVO a Swift property which isn't dynamic.
Yes, though I expect (hope?) that there is eventually something better than traditional KVO/bindings/etc coming along for Swift. (Note, for example, that did/willSet takes over a little bit of the KVO universe. Just not very much.) > If I have understood properly, up until beta 4 that also used objc_MsgSend > and was fully dynamic, as of beta 5 it may or may not use objc_MsgSend or it > may optimize around it. I got the impression that earlier betas might have optimized around it, and therefore that KVO wasn’t reliable. I think ‘dynamic’ is a bug fix. > if you write such a property in Swift and mark it only @objc then it's quite > possible Swift will call the original, unswizzled methods, and you won't get > your notification .. because objc_MsgSend may not be used Yes, I suppose if Swift decided to use a direct call, it would call the wrong thing, but not because of swizzling, since KVO doesn’t swizzle. Instead, it dynamically changes the class of your object to a synthetic class with a method that overrides your setter. So, the error in Swift’s “reasoning” would be that the method wasn’t overridden when it really was. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
