> On Mar 29, 2016, at 9:57 AM, Jordan Rose <[email protected]> wrote: > >>> >>> Is there a plan in place to deal with this? >> >> There are several discussions, but none of them are in scope for Swift 3. >> My recommendation is that you align with what we have in Swift 3, and if we >> do ever generalize the language and the rest of the stdlib, we can >> generalize autoreleasepool along with it. > > The weak link for me is the assertion that 'autoreleasepool' is more like > 'forEach' than 'withCString' or 'withUnsafeMutablePointer'. We've seen some > very nice simplifications by having those return values (usually replacing > optional 'var' with a non-optional 'let').
I’m not arguing against “utility” here. Perhaps the wedge is so strong for me, because @autoreleasepool *is* a statement in ObjC. -Chris _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
