Bob Roebling
Sep 3, 2018 · 1 min read

Sure, Apple states that you should always start with a struct then swap it out for a class when it makes sense. Here is a full article on how to decide which to use.

The biggest deciding factor for me is whether or not the object I want to create will need to derive some functionality from another class object. Only classes can inherit from other classes. However, both structs and classes can adopt from protocols.

    Bob Roebling
    Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
    Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
    Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade