|
|
|
|
|
|
by ralmidani
2169 days ago
|
|
|
Regarding language changes, I think this has improved quite a bit. I forget if stability was introduced in 4.x or 5.x, but code written today should be fine even when run through a new major version of the compiler. You can simply ignore new language features you aren't ready for until your codebase is due for a refactor. Regarding ARC, you don't have to use reference types in Swift, and the community seems to agree that structs are more suitable than classes for most use cases (a SwiftUI app is made of structs that conform to certain protocols, and those structs can be initialized, copied, and "modified" with little overhead). The cool thing about Swift is that structs can still have methods, computed properties, and custom initializers. So if you're coming from Python or Ruby or Java, or think OOP can help you organize your code, you don't have to throw away everything you've learned in order to be productive and write elegant code (and Swift brings a few new OOP tricks of its own). |
|
|
They've always provided source compatibility modes in new releases of the compiler so you can delay making syntax changes to an existing codebase if you need to.
You're thinking of ABI stability, which is in place as of Swift 5, and doesn't have anything to do with what parent is talking about.