Which of Swift 5.1 features are backwards deployable?

Pretty much everything in the language is backwards-deployable besides opaque result types, because as Max points out they compile down to existing constructs.

Pretty much everything in the standard library is not backwards-deployable because it has to exist at run time. A few fixes are set to be emitted into client apps instead of living in the stdlib, but that's not the common case.

10 Likes