Closed capnslipp closed 8 years ago
As of Xcode 8b6's Swift 3.0, closures are now non-escaping by default, so the @noescape keyword is no longer necessary, and deprecated (Xcode now emits on usages warning: @noescape is the default and is deprecated). More info on this change at https://github.com/apple/swift-evolution/blob/master/proposals/0103-make-noescape-default.md and http://adcdownload.apple.com/Developer_Tools/Xcode_8_beta_6/Release_Notes_for_Xcode_8_beta_6.pdf .
@noescape
warning: @noescape is the default and is deprecated
@escaping
This is cool. Thanks!
devxoul
commented
8 years ago
As of Xcode 8b6's Swift 3.0, closures are now non-escaping by default, so the
@noescapekeyword is no longer necessary, and deprecated (Xcode now emits on usageswarning: @noescape is the default and is deprecated). More info on this change at https://github.com/apple/swift-evolution/blob/master/proposals/0103-make-noescape-default.md and http://adcdownload.apple.com/Developer_Tools/Xcode_8_beta_6/Release_Notes_for_Xcode_8_beta_6.pdf .@noescapekeyword. Double-checked to make sure there were no formerly-escaping closures that would need the new@escapingkeyword.