Why would you want to create an empty collection?
Updated for Xcode 15
When you’re just learning Swift, it’s common to see examples such as this one:
let names = ["Eleanor", "Chidi", "Tahani", "Jianyu", "Michael", "Janet"]That’s a constant array of six strings, and because it’s constant it means we can’t add more things to the array – we know all our items when the array is created, so the rest of our program is just using that fixed data.
But sometimes you don’t know all your data up front, and in those cases it’s more common to create an empty collection then add things as you calculate your data.
For example, we have our fixed names array above, and if we wanted to figure out which names started with J then we would:
- Creating an empty string array called something like
jNames - Go over every name in the original
namesarray and check whether it starts with “J” - If it does, add it to the
jNamesarray.
When we’ve gone over all the names, we’ll end up with two strings in jNames: Jianyu and Janet. Of course, if our check was which names started with “X” then we’d end up with no names in the array – and that’s OK. It started as empty and ended as empty.
Later on in this book we’ll be looking at the Swift code needed to make all this work for real.
BUILD THE ULTIMATE PORTFOLIO APP Most Swift tutorials help you solve one specific problem, but in my Ultimate Portfolio App series I show you how to get all the best practices into a single app: architecture, testing, performance, accessibility, localization, project organization, and so much more, all while building a SwiftUI app that works on iOS, macOS and watchOS.
Sponsor Hacking with Swift and reach the world's largest Swift community!
