When should you omit a parameter label?

Paul Hudson    @twostraws    October 25th 2021

Updated for Xcode 14.2

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:

• Greeting a person would be greet(taylor) rather than greet(person: taylor)
• Buying a product would be buy(toothbrush) rather than buy(item: toothbrush)
• Finding a customer would be find(customer) rather than find(user: customer)

This is particularly important when the parameter label is likely to be the same as the name of whatever you’re passing in:

• Singing a song would be sing(song) rather than sing(song: song)
• Enabling an alarm would be enable(alarm) rather than enable(alarm: alarm)
• Reading a book would be read(book) rather than read(book: book)

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.

SAVE 50% To celebrate WWDC23, all our books and bundles are half price, so you can take your Swift knowledge further without spending big! Get the Swift Power Pack to build your iOS career faster, get the Swift Platform Pack to builds apps for macOS, watchOS, and beyond, or get the Swift Plus Pack to learn advanced design patterns, testing skills, and more.

Save 50% on all our books and bundles!