Steal from the Github style guide!

[gregheo]

GitHub have created their own guide here:

https://github.com/github/swift-style-guide

Good to see that we agree on quite a few syntax related points. However theirs is a lot more opinionated.

I am still trying to get my head around Swift structs and how widely to use them, notice that GitHub advise you to prefer structs over classes.

[hollance]

Here's how I think about structs vs classes:

You use structs for things that do not have an identity. An array that contains objects a, b, c is really the same as another array that contains objects a, b, c. Even though both arrays may be located in different memory locations, they are completely interchangeable. For the code it doesn't matter whether you use the first array or the second, because they represent the exact same thing. That's why array is a struct.

You use classes for things that do have an identity (as well as a specific life cycle). You would model a Person as a class because two persons are two different things. Just because two people have the same name and birthdate (or other attributes), doesn't mean they are the same person. But the person's birthdate would be a struct because a date of 3 March 1950 is the same as any other date object for 3 March 1950. The date itself doesn't have an identity.

(Of course, if you use NSDate then the date is a class but that's because of Objective-C.)

[ColinEberhardt]

BUMP

We really should get this text included somehow!