Lines Matching full:autorelease
169 simplify certain operations, there is also an :arc-term:`autorelease pool`, a
171 added to this pool by calling ``autorelease`` on it.
306 * ``autorelease``, taking no arguments and returning a pointer to the object.
329 The behavior of ``autorelease`` must be equivalent to sending ``release`` when
330 one of the autorelease pools currently in scope is popped. It may not throw an
485 call boundary. In the worst case, this may involve an ``autorelease``, but
486 callers must not assume that the value is actually in the autorelease pool.
502 autorelease pool. There are no additional semantics enforced in the definition
925 Autorelease pools are tied to the current thread and scope by their nature.
931 ``__autoreleasing`` object while an autorelease pool is in scope and then that
932 object is read after the autorelease pool's scope is left.
1304 * outside of ARC, the instance methods ``retain`` and ``autorelease``
1559 * ``autorelease``
1665 To simplify the use of autorelease pools, and to bring them under the control
1669 of the autorelease pool is captured. When the block is exited normally,
1671 ``break``), the autorelease pool is restored to the saved state, releasing all
1682 Autorelease pools are clearly important for the compiler to reason about, but
1685 to drain an autorelease pool when using the manual API, and this can
1819 * the autorelease pool is restored to a previous state.
1831 The extension rules are somewhat intentionally vague. The autorelease pool
1833 autorelease the receiver. The other limit permits some amount of
1979 to the innermost autorelease pool exactly as if the object had been sent the
1980 ``autorelease`` message.
1994 Releases all the objects added to the given autorelease pool and any
1995 autorelease pools it encloses, then sets the current autorelease pool to the
2003 Creates a new autorelease pool that is enclosed by the current pool, makes that
2180 operation followed by an autorelease operation. Equivalent to the following
