You have serious speed optimization here. Creating an array is expensive. Instead, you get an instance of some weird class that behaves like an array. However, it does not have its data stored in a real array; instead, it gets access to data from the dictionary.
Say you have a dictionary with 10,000 string values. You don't want iOS to copy all 10,000 string values when you call dict.values, right? This is what this class is for, to prevent copying of 10,000 lines. A real array will force copy.
In general, with your username you ask for such things, and Apple provides many examples. This is how they quickly make iOS.
source share