ios - init中返回nil会导致内存泄漏吗？

Question

当[super init]已经被调用，然后返回nil时，在init中的ARC下返回nil会导致内存泄漏吗？这是合法的用法吗？

- (id)init {
   self = [super init];
   if (self) {

       ...
       return nil;
       ...

   }
   return self;
}

Answer 1

首先:对于涉及 ARC 的 Q，从来没有阅读过 Apple 的文档，而是 clang 的文档。

Apple 的文档只是隐藏了(隐藏？)-init 的执行，并且有这样的错误示例:

id ref = [[Class alloc] init]

您会发现有一条类似“+alloc 转移所有权”的语句。这至少会产生误导，因为存储的是 auf -init 的返回值，而不是 +alloc 的返回值。

clang 的文档到目前为止更好、更精确。基本上他们说，+alloc 是所有权转移，，-init 是所有权消耗和所有权转移。

http://clang.llvm.org/docs/AutomaticReferenceCounting.html#semantics-of-init

Methods in the init family implicitly consume their self parameter and return a retained object.

让我们看一下常用的代码:

id ref = [Class alloc]; 
// ref is strong: RC is +1;
id ref = [ref init];    
  // Three things happen her:
  // 1. -init is executed
  // 2. The new value is stored
  // 3. The old value of ref is lost

  // 1. -init is executed
  // self is (silently) passed to the receiver
  - (id)init           
  {
    // Since self is strong (+1), RC is +2 now
    // Since -init is ownership consuming (-1), RC is +1 now
    …
    return self;
    // Since -init is ownership transferring (+1), RC is +2 now
  }

  // 2. The new value is stored
  // The value comes from an ownership transfer method, so the assignment to strong ref is neutral (0), RC is still +2

  // 3. The old value is lost (-1), RC is +1

结果是该对象的 RC 为 +1，并且您在该代码区域中对其有一个强引用。一切安好。 (当然，优化的潜力很大，因为在大多数情况下，self 和 ref 都没有改变，但让我们保持常规轨道。)

让我们在 -init 中更改 self:

id ref = [Class alloc]; // Ownership transfer. RC is +1;
id ref = [ref init];    
  // Three things happen her:
  // 1. -init is executed
  // 2. The new value is stored
  // 3. The old value of ref is lost

  // 1. -init is executed
  //     self is (silently) passed to the receiver
  - (id)init           
  {
    // Since self is strong (+1), RC is +2 now
    // Since -init is ownership consuming (-1), RC is +1 now

    // Let's return nil as in your example
    return nil;
    // Because nil is returned, virtually the RC of nil is increased. self's RC == +1 is unchanged.
  }

  // 2. The new value is stored
  // The new value is nil.
  // However the value comes from an ownership transfer method, so the assignment to strong ref is neutral (0), RC is still +1

  // 3. The old value is lost (your old ref and the self while executing -init) (-1), RC is 0
  // The old object is dealloced, if you do not have another ref to it. Nothing leaks.