> On 6 Feb 2015, at 21:31, Greg Parker <gpar...@apple.com> wrote: > >> Come to think of it, I'm surprised that AppKit delegates are still >> unsafe-unretained. Why haven't these been converted to safe weak references >> yet? > > Some classes are incompatible with (safe zeroing) weak references. For > example, any class that implements custom retain count storage needs > additional code to work with weak references. That means AppKit needs to be > careful about binary compatibility when it changes an unretained delegate to > a weak delegate. > Does Swift avoid unsafe-unretained references entirely or does it rear its head when interacting with Obj-C?
J _______________________________________________ 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
