Design Converter
Flutter
React
Shopify
Flutter
React
Shopify
Discord
Discord
Education
Software Development Executive - III
Last updated on Jul 10, 2024
Last updated on May 30, 2024
Swift Closure, a self-contained block of functionality that you can pass around in your code, emerges as a powerful concept to master in Swift development. Swift closures encapsulate blocks of code, which can be called later, often as a form of callback, or to keep related code together. Understanding closures not only enables you to write more concise and readable code but also lets you leverage Swift's full potential.
With the capability to capture and store references to constants and variables from the surrounding context in which they are defined, closures play a key role in Swift programming. They are similar to blocks in C and lambdas in other programming languages but with cleaner and more flexible syntax tailored to Swift.
Closures in Swift come in several forms: named closures similar to functions, unnamed closures written as inline closure expressions, and closure arguments passed to functions that can capture and store references to any constants and variables from their surrounding context. By the end of this section, you should have a solid grounding in what Swift closures are and why they are indispensable in Swift programming.
Swift closure syntax is distinct and often markedly more succinct than the equivalent function syntax. A basic closure in Swift is written with a pair of curly braces () and resembles a function without a name. Let's break down the syntax:
1{ (parameters) -> ReturnType in 2 // Closure body 3}
At its core, the Swift closure syntax consists of the in keyword, which is used to separate the closure's parameter list and return type from the closure's body. Within the closure's functionality immediately, the actual statements to execute are enclosed.
For instance, here is a simple Swift closure example that takes two Int values and returns their sum:
1let sumClosure: (Int, Int) -> Int = { (a: Int, b: Int) -> Int in 2 return a + b 3}
The closures provide the benefit of inferring parameter and return types from context, which means you can often write closures in a shorter form known as shorthand argument names. This, combined with implicit returns from single-expression closures that don't include the return statement, makes closures swift and efficient.
Swift closure syntax supports several simplifications that will enable you to write more concise code. For instance, if the context already provides type information, such as when you pass a closure as a function argument, then the types of closure parameters, the return type, and the in keyword can all be omitted:
1let sumClosure = { (a, b) in a + b }
Understanding and mastering the swift closure syntax will streamline how you handle functions that take several closure arguments and how you utilize closures as completion handlers or for other asynchronous operations.
To give you a sense of how swift closures work in practice, let’s walk through some simple examples. Consider a situation where you have an array of integers and you want to sort them in descending order. Using Swift's sort() method with a closure makes this task straightforward:
1let numbers = [20, 10, 40, 30] 2let sortedNumbers = numbers.sorted(by: { (first: Int, second: Int) -> Bool in 3 return first > second 4})
Another common use for closures is to perform actions with elements in a collection using methods like map, filter, and reduce. For instance, to double each number in the array and generate a new array, you'd write the following using a closure:
1let doubledNumbers = numbers.map({ number in number * 2 })
The power of swift closures becomes even more evident with trailing closures. When passing a closure as the last argument to a function, Swift lets you write it outside the function call's parentheses for increased readability:
1let reversedNumbers = numbers.sorted { $0 > $1 }
In this example, shorthand argument names are used (i.e., $0 and $1), showcasing how concise closure expressions can be. Remember, you can use these shorthand argument names when the function defines the expected function type, and Swift can infer the parameters from it.
Continuing with another swift closure example, consider a network request where you might use a closure as a completion handler to handle the response:
1NetworkManager.fetchData { data, error in 2 guard let data = data else { 3 print("Error:", error?.localizedDescription ?? "unknown error") 4 return 5 } 6 // Process the fetched data 7 print("Data received: \(data)") 8}
In this swift closure example, the block is used to handle the asynchronous result of fetchData. This pattern is common when dealing with asynchronous tasks such as networking calls, where you want to execute a closure's functionality immediately after an operation completes without blocking the main thread.
Moving deeper into closure expressions, they represent an inline closure that's written within the context of a larger expression. The inline closure expression serves as a self-contained block of code without a function name, intended to be used where a function is expected.
For example, consider a scenario where you have a method that takes a closure as an argument label, such as UIView.animate:
1UIView.animate(withDuration: 1.0) { 2 // Inline closure body that runs during the animation 3 view.alpha = 0 4}
In this case, the inline closure modifies the view's alpha property over a one-second interval. The aforementioned inline closure expression greatly simplifies the syntax, as you don’t need to define a separate named function elsewhere.
Closure expressions can be more complex, involving decisions or loops, and they can be lengthy when they include detailed logic. Here's how you might create a closure that filters an array:
1let names = ["Alice", "Bob", "Charlie", "David"] 2let namesStartingWithC = names.filter { (name) -> Bool in 3 return name.hasPrefix("C") 4}
Again, our closure expression here is concise thanks to type inference and contextual cues. Even though the closure's argument list and the return type can be inferred by Swift, it's sometimes important to write the explicit closure for clarity, especially when the closure is complex.
Trailing closures are a unique Swift feature that allows you to make your code more readable by placing the closure expression outside of, and immediately after, the parentheses of the function call. When a function takes a closure as its last parameter, the trailing closure syntax lets you omit the argument label.
Here is an explanation of trailing closure syntax with a trailing closure in action:
1someFunctionThatTakesAClosure() { 2 // Trailing closure's body goes here 3}
When you use the trailing closure syntax, the closure is still part of the function call but it's written after the method's outer parentheses. For functions that take multiple trailing closures, you can specify each closure one after the other:
1someFunctionWithMultipleClosures(firstClosure: { 2 // First closure's body 3}) secondClosure: { 4 // Second closure's body 5}
The trailing closure syntax simplifies and improves readability, allowing the same closure to appear less complex and more like a structured block of code. Now, let’s see trailing closures in action with a real-world example, such as a UIView animation:
1UIView.animate(withDuration: 1.0) { 2 // Trailing closure with animation changes 3 view.alpha = 1 4} completion: { finished in 5 // Trailing closure with code to run on completion 6 print("Animation finished: \(finished)") 7}
Notice how the trailing closure syntax makes it clear that the closures are related to the animation and its completion without cluttering the function call itself. The same principles apply when using multiple trailing closures.
It's essential to differentiate Swift block syntax from closure syntax, as closures are often confused with blocks or lambdas found in other programming languages. Swift closures are first-class citizens, meaning you can pass them as arguments, return them from functions, and store them as variables.
While blocks in Objective-C, for instance, look and behave similarly to Swift closures, they have a distinct syntax and form. A swift block syntax might come off as this:
1^ReturnType(parameters) { 2 // Block body 3};
This differs from a swift closure, which lacks the caret (^) symbol, opts for the in keyword, and encourages various syntactic shortcuts that reduce verbosity.
Closures in Swift, through their simplified syntax and capturing capabilities, provide a robust way to write self-contained blocks of functionality that can interact with their surrounding context without the overhead and complexity of blocks in Objective-C and some other programming languages.
Beginning with Swift 5.3, you can provide multiple trailing closures within a single expression. This addition to the language improves syntax clarity when a function call includes more than one closure. Here is how multiple trailing closures work:
1func performAction( 2 withCompletion completion: () -> Void, 3 onFailure failure: () -> Void) { 4 // Perform some action 5} 6 7// Using the function with multiple trailing closures 8performAction { 9 // completion closure body 10 print("Action Succeeded") 11} onFailure: { 12 // failure closure body 13 print("Action Failed") 14}
In the code snippet above, multiple trailing closures significantly enhance readability by separating the function's logic for completion and failure into distinct blocks. They also make it clearer which closure corresponds to each parameter of the function.
The introduction of multiple trailing closures was a meaningful evolution in Swift, as it allowed developers to clean up their syntax even further, especially when dealing with SwiftUI or UIKit APIs that commonly use closures for configuration.
For instance, SwiftUI's Button initializer takes multiple trailing closures to handle different states, like so:
1Button(action: { 2 print("Button was tapped") 3}) { 4 // Provide the button's label 5 Text("Tap me!") 6} 7// In future SwiftUI versions, there might be additional trailing closures for different button states
In this scenario, the use of multiple trailing closures allows for a clear distinction between the action the button performs and its content or label. Notice that there is no need for an argument label for the first trailing closure, as it naturally follows the function call's parentheses. However, for any remaining trailing closures, labels are required to specify which closure corresponds to which function parameter.
By integrating multiple trailing closures into Swift functions, Apple has streamlined how developers construct complex UI elements, manage asynchronous tasks, and more. It introduces a level of syntactic flexibility that can make code not only more enjoyable to write but also easier to read and maintain.
Closures become particularly useful when managing asynchronous tasks in Swift, like network requests or database calls. They allow for executing a closure's functionality immediately after a task finishes, without blocking the execution of the main thread.
For example, consider an escaping closure, which is a closure that's passed as an argument to a function and invoked after the function returns:
1func fetchData(completion: @escaping (Data?, Error?) -> Void) { 2 // Asynchronous fetch logic 3 let data = // ... some data 4 let error = // ... some error 5 DispatchQueue.main.async { 6 completion(data, error) 7 } 8}
In an escaping closure, we need to tell Swift that our closures should be allowed to escape, meaning they can be stored and executed later on, which has implications for memory management. When you capture and store references to constants, variables, or self within an escaping closure, Swift ensures everything is managed correctly under the hood.
This is a cornerstone concept for implementing completion handlers in Swift. In concurrent programming, it's fundamental to understand how escaping closures capture values from their context to avoid retain cycles and memory leaks.
Capturing values typically involves taking whatever constants and variables you want access to and using them within the body of a closure. Swift smartly manages the process and all memory management involved through a capture list when necessary, to define the rules of how values are captured:
1func performNetworkRequest(_ handler: @escaping (Result<Data, Error>) -> Void) { 2 // Some network request logic 3 networkRequest.start { result in 4 handler(result) 5 } 6}
With the introduction of Swift's concurrency model, you also have the alternative to use async/await patterns where previously you might have used closures. However, escaping closures remain prevalent, especially within APIs and older Swift codebases.
Swift's standard library lends itself to functional programming paradigms, with closures being pivotal when working with collection types like arrays, dictionaries, and sets. Using closures within higher-order functions like map, filter, and reduce allows you to articulate complex operations clearly and concisely.
Consider applying a transformation to every array element in a collection. With closures, the map function becomes a powerful tool to achieve such an operation:
1let numbers = [1, 2, 3, 4, 5] 2let squaredNumbers = numbers.map { $0 * $0 } 3print(squaredNumbers) // Prints: [1, 4, 9, 16, 25]
In this concise expression, we're using an inline closure with shorthand argument names ($0) to provide an alternative mapped value for each element in the array. Similarly, closures allow you to filter elements based on a condition:
1let evenNumbers = numbers.filter { $0 % 2 == 0 } 2print(evenNumbers) // Prints: [2, 4]
With closures swift, achieving a cumulative result such as a sum is straightforward with reduce:
1let sum = numbers.reduce(0) { $0 + $1 } 2print(sum) // Prints: 15
Here, we're using a closure as the combining function for reduce, starting from zero and adding each array element to the total. This use of closures showcases their utility in both simplifying the code and keeping it expressive.
Closures also excel in more advanced collection operations, such as chaining. It is quite common to chain closures together to perform complex transformations and computations in a clean, readable manner:
1let formattedNumbers = numbers 2 .filter { $0 % 2 == 0 } 3 .map { "Number \($0)" } 4 .joined(separator: ", ") 5 6print(formattedNumbers) // Prints: "Number 2, Number 4"
This snippet filters for even numbers, transforms each number into a string, and then joins them with a comma. The efficient use of chained closures avoids additional loops and temporary variables, highlighting the strength and elegance of Swift's functional programming capabilities.
Closures in Swift can also take advantage of capturing values, which means they can capture and store references to variables and constants from the lexical scope they appear in. This feature is incredibly useful when you want a closure to hold onto a value and use it later, typically when the value is no longer in scope:
1func makeIncrementer(forIncrement amount: Int) -> () -> Int { 2 var runningTotal = 0 3 return { 4 runningTotal += amount 5 return runningTotal 6 } 7} 8 9let incrementByTwo = makeIncrementer(forIncrement: 2) 10print(incrementByTwo()) // Prints: 2 11print(incrementByTwo()) // Prints: 4 12print(incrementByTwo()) // Prints: 6
The incrementByTwo closure captures the runningTotal variable. Each call to incrementByTwo increments the runningTotal by two, demonstrating how closures capture and store state.
When working with collections, closures also serve as a bridge to Swift's vast ecosystem of operator methods, like sort(by:), forEach, and many more, allowing for fluent and intuitive manipulation of elements, all while adhering to Swift's elegant type system.
Throughout this article, we've unraveled the mystery of Swift closures and how they offer a versatile toolset for encapsulating blocks of functionality. From simplifying callbacks to transforming collections, closures open a gateway to a more functional programming approach.
We've covered swift closure syntax and practical examples, the readability benefits offered by trailing closure and multiple trailing closures, the distinctions between closures and block syntax in other programming languages, and the use of closures in concurrent programming and collections.
Embracing swift closures will not only enhance your coding style but also allow you to write more expressive, maintainable, and succinct Swift code. So, embrace closures in your daily coding practices and harness their full potential to develop robust and elegant applications.
Tired of manually designing screens, coding on weekends, and technical debt? Let DhiWise handle it for you!
You can build an e-commerce store, healthcare app, portfolio, blogging website, social media or admin panel right away. Use our library of 40+ pre-built free templates to create your first application using DhiWise.
