When to use a set rather than an array

Swift version: 5.6

Paul Hudson    @twostraws    November 28th 2019

Sets and arrays both store objects of your choosing, but they have four important differences:

1. Sets do not store objects in the order they add them.
2. Instead, they are stored in a way to make them fast to find, which means finding items in sets is extremely efficient.
3. Sets store each item precisely once.
4. All items you want to store in a set must conform to Hashable.

As a result, you should use a set rather than an array if all the following criteria are true:

1. You intend to add each item only once. Sets never allow duplicates.
2. You don’t care about the order of the items in the set.
3. You don’t need to use APIs that require arrays.
4. You’re storing Hashable types, either your own or one of Swift’s built-in types likes strings and integers. Sets use hash values for fast look up of items.

You can switch between an array and a set simply enough:

let array = [1, 2, 3]
let set = Set(array)
let array2 = Array(set)

Using contains() on a set takes the same amount of time if you have one item as it does if you have one thousand items – it’s called an O(1) operation.

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.

Explore the docs

Sponsor Hacking with Swift and reach the world's largest Swift community!

Available from iOS – learn more in my book Pro Swift

Similar solutions…

• SwiftUI tips and tricks
• How to give UITableViewCells a selected color other than gray
• What’s the difference between @ObservedObject, @State, and @EnvironmentObject?
• How to count objects in a set using NSCountedSet
• All SwiftUI property wrappers explained and compared

About the Swift Knowledge Base

This is part of the Swift Knowledge Base, a free, searchable collection of solutions for common iOS questions.