Swift 5 release about deferred HOT 8 CLOSED

Deferred supports the range of Swift versions our clients are using. The final release of Deferred 4.0 will be specifically compatible with Swift 4.1, 4.2, and 5.0 compilers by using syntax that is common to all 3. Swift has supported multiple dialects in this way since Swift 4.

Compiling Deferred 4.0 using a Swift 5 compiler nets all the benefits of Swift 5, including use of the stable ABI. Likewise, compiling Deferred 4.0 against the planned Swift 5.1 will grant module stability and allow shipping binary releases of Deferred — still with no code changes needed.

After cutting the 4.0 release, we will likely move on master to drop Swift 4.1, but certainly won't be dropping Swift 4.2 until Swift 5.0 has gone stable.

For its part, CocoaPods does not allow us to express this range of support without a feature that has only just now entered beta: CocoaPods/CocoaPods#8191.

from deferred.

Agreed, CocoaPods support is behind.

But this is what I was referring to: shouldn't the preferred Swift version (set via the podspec) be set to at least 4.2?

from deferred.

We are choosing to support Swift 4.1, so no.

from deferred.

Hey, I'm trying out the 4.0 final release and it looks like when building using Xcode 10.2 and setting the Swift version to 5 it's not compiling due to some outdated annotations:

I have seen that the CI has passed on Swift 5 with Linux so I don't know if there's an extra flag I should set to benefit from Swift 5 here.

As always: thank you!

from deferred.

Changing the version is not necessary to benefit from the Swift 5 compiler.

The next point release of Deferred will adjust the language version appropriately.

from deferred.

Would this mean that the final App that links Deferred would reduce in size due to using the built-in Swift libraries when available (iOS 12.2+)?

from deferred.

Yes.

from deferred.

Ok! Thanks!

from deferred.