> On Jul 12, 2017, at 10:38 AM, Charles Srstka <cocoa...@charlessoft.com> wrote: > > While that’s true, the main reason, as I understand it, that ARC doesn’t know > enough about the object’s lifetime is that non-ARC code may be calling the > method. In an all-ARC world, a method could always just return objects with a > +1 retain count, and the consumer could just assume that and always balance > the retain.
It could, but that results in _enormous_ numbers of retain/release calls. (I speak from some experience, having once worked on performance optimization of a project that did ref-counting this way.) It’s generally cheaper overall to use autorelease, and that was one of the reasons NeXT invented it* (besides the obvious benefit of simplifying MRR code.) —Jens * I’m not actually sure they did; there’s an earlier technique called “deferred reference counting” that might be equivalent. _______________________________________________ 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
