vishalvshekkar / archivingswiftstructures

A comparison and demonstration between 3 ways of archiving and unarchiving Swift Structures. The playground ArchivingSwiftStructures1 is the most inelegant way of doing this. Look at ArchivingSwiftStructures2 and ArchivingSwiftStructures3 for more elegant ways. Swift made structures very powerful, and hence using structures more is very tempting. But, since NSCoding can only be conformed to by classes, archiving structure instances needs some workaround. Read through my article detailing ways to do this here: https://medium.com/@vishalvshekkar/swift-structure-instances-within-a-class-archived-with-nskeyedarchiver-e27744f26811#.a7k5jwl4a

I'm Vishal, Hi.

As a technologist who is passionate about creating products that invoke emotions, I have helped build over 20 products. I deeply involve myself in the architecture, planning, and development phases of products that employ both machine learning and platform development technologies. In my free time, I dabble in design and collect vinyl records.

Currently

• Heading Tech at Labyrinth.
• Working on NextHub. Download it on the App Store.
• Working on Cacti. Download it on the App Store.
• Working on Dialogue. Download it on the App Store.
• Working on Retain, an opinionated S3 client for iOS, iPadOS, and macOS. Coming out soon.

---

• Ask me about managing tech teams, machine learning, design, scaling tech platforms, encryption, and Swift.
• I'm passionate about privacy, online security, good design, and egalitarianism.
• Cofounded: Labyrinth and Verizy.
• How to reach me: vishalvshekkar.com
• Find more of my work on GitLab.
• Pronouns: he/him

archivingswiftstructures's Issues

Problem with Swift 3

I updated to Swift 3 and after conversion it looks like I cannot read the archived struct.
Any idea what I did wrong?