I have an extension Array
in the form of:
extension Array
{
private func someFunction(someClosure: (() -> Int)?)
{
// Do Something
}
func someOtherFunction(someOtherClosure: () -> Int)
{
someFunction(someClosure: someOtherClosure)
}
}
But I'm getting the error: Passing non-escaping parameter 'someOtherClosure' to function expecting an @escaping closure
.
Both closures are indeed non-escaping (by default), and explicitly adding @noescape
to someFunction
yields a warning indicating that this is the default in Swift 3.1.
Any idea why I'm getting this error?
The problem is that optionals (in this case
(()-> Int)?
) are an Enum which capture their value. If that value is a function, it must be used with@escaping
because it is indeed captured by the optional. In your case it gets tricky because the closure captured by the optional automatically captures another closure. SosomeOtherClosure
has to be marked@escaping
as well.You can test the following code in a playground to confirm this:
As already said,
Optional
closures areescaping
. An addition though:Swift 3.1 has a withoutActuallyEscaping helper function that can be useful here. It marks a closure
escaping
only for its use inside a passed closure, so that you don't have to expose theescaping
attribute to the function signature.Can be used like this:
Hope this is helpful!
Optional closures are always escaping.
Why is that? That's because the optional (which is an enum) wraps the closure and internally saves it.
There is an excellent article about the quirks of
@escaping
here.