Updated for Xcode 14.0 beta 1
If we use an underscore for a function parameter’s external label, Swift lets us use no name for that parameter at all. This is very common practice in some parts of Swift development, particularly when building apps that don’t use SwiftUI, but there are many other times when you’ll also want to use this.
The main reason for skipping a parameter name is when your function name is a verb and the first parameter is a noun the verb is acting on. For example:
This is particularly important when the parameter label is likely to be the same as the name of whatever you’re passing in:
Before SwiftUI came along, apps were built using Apple’s UIKit, AppKit, and WatchKit frameworks, which were designed using an older language called Objective-C. In that language, the first parameter to a function was always left unnamed, and so when you use those frameworks in Swift you’ll see lots of functions that have underscores for their first parameter label to preserve interoperability with Objective-C.
SPONSORED In-app subscriptions are a pain. The code can be hard to write, hard to test, and full of edge cases. RevenueCat makes it straightforward and reliable so you can get back to building your app.
Link copied to your pasteboard.