During migrations, you’re likely to encounter unexpected challenges. Some questions might have been addressed in this course, while others remain unanswered. While I’m trying to keep this course up to date, it’s also a fact that Swift is constantly evolving. Therefore, I’ll use this lesson to address frequently asked questions that are too small to warrant a dedicated lesson.

Since the course is still young, there aren’t many questions listed here yet. Additionally, some questions may not be addressed here but will instead be converted into new lessons or lesson updates. For these, you’ll always get an email update.

I have a question, where can I ask this one?

I’d love for you to open an issue on the course GitHub repository.

When do I know it’s the right time to migrate?

This depends entirely on your project’s timeline and whether a significant deadline is approaching. A continuous migration works best. In between feature development, you’ll progressively apply improvements to your codebase that contribute to a migration to Swift 6 and strict concurrency.

Ideally, you’d open issues for parts that still require migration. Even better would be to indicate how long you expect those migrations to take. This allows you to pick up tickets progressively, but also at moments where you might have 30 minutes left at the end of the day for some low-hanging fruit.

Will we ever be forced to migrate to Swift 6?

We’ve never been forced to migrate to any version in the past, but you can assume that new updates of Xcode will eventually drop support for Swift 5. You also want to benefit from the latest improvements coming to Swift, so I’d like to answer this as: no, but you should still plan to migrate to Swift 6.

Summary

While it’s weird to write a summary for a FAQ, I love consistency at the same time. Therefore, this is just a short summary to give you a heads up about the assessment that’s coming up next. Good luck!