My last entry on escaping closures ended up having way more interaction than I anticipated! It goes to show that you never know what the impact of a piece of writing will have. But that’s a different story… :]
Several readers commented here and on Medium with the question, “Why? Why do we need to mark escaping closures with
Do it yourself, compiler!
Observant minds looked at the compiler’s ability to say, “Hey! This closure can escape – Annotate it with
@escaping!” and asked, “Well… why?? If you, compiler, are smart enough to figure out that I need to annotate it, why can’t you just deal with it automatically and let me go about my business?”
And one that I didn’t know the answer to. So I researched!
Insight from the Swift gurus
The compiler has enough logic in it to provide a great QoI (Quality of Implementation) experience when a developer doesn’t think about escaping, and tries to escape a closure – it can provide a fixit that suggests adding @escaping.”
Did you catch that?
When the Swift compiler requires us to annotate our APIs with
@escaping, that’s its way of doing “quality of implementation”.
Essentially, it’s a red flag saying, “You really ought to think about this whole escaping thing that you just introduced (whether you knew you were doing it or not)… it has significant impact on your implementation and on the caller of your function!”
I see what you did there… Let me help you out…
The Swift compiler, for better or worse, wants to be very… “helpful”…
Some people hate it. I love it.
I want to be told, “Hey, Andrew… you’re about to break stuff – don’t do that.”
I’d rather head off issues during development than at run-time.
How helpful is it, really?
But really… How helpful is this particular compiler error? What value does this fix-it option provide?
Try this: Think about what would happen if the compiler didn’t tell you about the possibility of your function’s closure escaping.
I was working the other day, cruising along writing what I thought was perfectly normal code when I hit this “annotate your function’s closure parameter with
@escaping” error, myself.
@escaping, Huh? What’s that?!”
1 – I wasn’t thinking about escaping closures because
2 – I had no idea that I could think about escaping closures!!
It turns out that this could have been really bad, agreed? Asynchronous behavior in software requires a little more thought than your normal top-down procedural approach.
If the compiler hadn’t stopped me, I could have inadvertently imposed the need to think in terms of dispatch queues or asynchronous callbacks on the users of my API.
Is this only something that “newbies” need to have the compiler’s help with though?
One could argue that I probably should have been aware of this particular feature of Swift — had I been a better developer, maybe I wouldn’t need the compiler to hold my hand so much.
Okay – Fair point. That leads me to one last gleaning from Lattner’s Swift Evolution entry that I’ll comment on before wrapping up.
Writing resilient code
Let me reflect really quickly on one more quote from the Swift Evolution entry before I end for today.
John McCall pointed out that resilience in the type system is different than resilience in practice: An API changing to capture a closure and use it long after it was originally passed is likely to break the clients regardless of whether the type system captures this as an issue. He argues (and the argument is strong IMO) it is better for resilient APIs to default to @noescape, since that forces the author of V2 to think about whether they are breaking their clients. (emphasis mine)
Resilience is all about how clients are affected when you change the API or its implementation.
Suppose that a team mate of mine writes a function… She’s just created an API, true?
Suppose that the function asks for a closure, but for now it’s just a regular old closure. No escaping or anything.
Others on my team are going to start coding against that function’s signature. If the function is honest, it allows me and my team to have expectations about what it’ll do when it executes.
Now suppose that I’m going to work on version 2 of that same API. Only now, I’m going to introduce the opportunity for that closure to escape (maybe intentionally, or maybe accidentally out of ignorance).
Thaaaat’s gonna break my team. For sure.
They’re using the API as it is expecting normal synchronous behavior from the function. Now I’ve gone in and fundamentally changed what their expectations should be.
In other words, I haven’t been very resilient.
The default behavior of closures passed to functions is to be
@noescape. If I introduce the possibility for that closure to escape, I need to be red-flag warned about that, because I need to come up with some way to communicate this breaking change to the clients of the API. And/or provide an alternative so that clients of API v1 can still use it as expected.
Most of all, I need to think about the implications of what I’m doing, and sometimes (a lot of the times) that takes prompting.
The bottom line – The compiler is making you think
All of this to say: The compiler is making you think. Not only that, it’s forcing you to conform.
From what I’ve found, that’s the idea behind “why” we need to mark escaping closures with
@escaping in Swift.