> Further you can link 3.2 and 4.0 binaries together.
Do you have a source for this? This would imply ABI stability, which isn't being promised until Swift 5.
Re:Swift 5: start your engines
by slavapestov on Wednesday August 09, 2017 @05:19PM
(#14973723)
Swift "3.2" and 4.0 are really the same compiler, run with -swift-version 3 and -swift-version 4 flags, respectively.
I get that they're the same command-line tool, but as a bystander that doesn't tell me whether it's implemented underneath as two separate incompatible compilers that are toggled between with a flag. And even if it's a single compiler with mostly shared components, that doesn't have to imply that the binaries that are produced are ABI-compatible between the two. I'm not implying that I cannot believe that this use-case will work, only asking for some assurance from the compiler devs that it does.
Re:Swift 5: start your engines
by slavapestov on Thursday August 10, 2017 @02:02AM
(#14976884)
> I'm not implying that I cannot believe that this use-case will work, only asking for some assurance from the compiler devs that it does.
You have my assurances that it works ;-)
-swift-version 3 really just turns on some different paths through the parser and type checker to allow previously-valid Swift 3 code to survive to code generation time.
They're both compatible
Swift 5 is about having a stable binary interface so you can link against pre-compiled code going forward. In other words a Swift 6/7/8 binary can link against one compiled with Swift 5.
The bar for source breaking changes is also much higher than the already high bar in Swift 4. We may not see any source breaking changes in Swift 5.