Use direct access in partially constructed states, regardless of ARC: – (id)initWithReminder:(Reminder*)reminder_ { self = [super init]; if (self) { reminder = reminder_; // OR reminder = [reminder_ retain]; } return self; } This is because self.whatever will trigger other side effects, such as Key-Value Observing (KVO) notifications, or maybe your class implements (explicitly) or … Read more
From the assembly code it can be seen that accessing weakPtr generates a objc_loadWeak call. According to the Clang documentation, objc_loadWeak retains and autoreleases the object and is equivalent to id objc_loadWeak(id *object) { return objc_autorelease(objc_loadWeakRetained(object)); } This (hopefully) explains why both if(strongPtr == weakPtr) … and NSLog(@”weakPtr: %@”, weakPtr); create additional autoreleased references. This … Read more
Arc‘s documentation says: Shared references in Rust disallow mutation by default, and Arc is no exception: you cannot generally obtain a mutable reference to something inside an Arc. If you need to mutate through an Arc, use Mutex, RwLock, or one of the Atomic types. You will likely want a Mutex combined with an Arc: … Read more
Is it a bad idea to use the dot notation to initialize retain properties to nil in my init methods? Yes, it is a bad idea. 1) The object has already been zeroed in the alloc+init sequence, so it is not necessary to assign it nil. In other words, this call is useless unless you … Read more
The basics: What are the official reasons to not use retainCount? Autorelease management is the most obvious — you have no way to be sure how many of the references represented by the retainCount are in a local or external (on a secondary thread, or in another thread’s local pool) autorelease pool. Also, some people … Read more