So if you haven't given up on it yet and can't wait for the new diagnostics why not give it a try right now? Installing alternative Toolchainįrom the official Swift website we can download snapshots from the master branch which are rather not recommended for our daily development as they have not gone through the full testing that is performed for official releases. But it might be still worth installing.Įveryone that has tried SwiftUI has probably noticed how hard it is sometimes to find an issue with our code as the error messages are misleading most of the time. Just keep in mind that to submit your application to the App Store you must build it using the version of Swift that comes included within Xcode - using default toolchain that is. All we have to do is install the alternative toolchain that is available to download from website. Xcode comes by default with the latest stable toolchain release of the Swift, thankfully it supports using alternative toolchains instead of default one out of the box. version 11.3 of Xcode is now like 16 GB? That's quite a lot and having like 2 or even 3 versions of Xcode installed might not be possible for some of us, especially if one uses his MacBook not just for single project development but also for some other stuff as well. How can we give a new Swift version that has not been released with the latest available Xcode yet? Or maybe you are short on free disk space (sooner or later we all know that feeling I think 😭) and do not want to install a new version of Xcode yet? Toolchains take way less space (around 2-3 GB) compared to Xcode. Usually, we can compile them anyway with backward compatibility by setting older Swift versions for that framework but sometimes the new version of Swift brings a great addition that it is just too good not to use that.

Especially if your application depends on some third party frameworks since those will rather sooner than later be updated to support the new Swift version.

Even though we, developers, are not forced to use the newest Swift version right away when it is released it might be still good to be ready for it. Most important, however, we want to prepare our applications for a new Swift version. New releases do not only contain some minor fixes and improvements but we also often get some new features as well. Swift development isn't slowing down in any way new versions are being released a few times a year.

Older xcode