Progress toward the Swift 6 language mode

[stuchlej (Mikoláš Stuchlík)]

@hborla

Additional evolution proposals may include source-incompatible changes for Swift 6, and the Language Steering Group will evaluate such proposals on a case-by-case basis for high value to the language relative to the cost of source incompatibilities.

@jrose I have recently stumbled upon your post on the Forum regarding Opaque Pointer. There was a discussion whether correction of this problem might appear in Swift 6 and you have stated, that

@jrose

It’s hard to say. Swift versions apply on a per-library basis, so that you can use Swift 6 while still depending on a Swift 5 package. But what happens when the Swift 5 library vends an API that uses one of these OpaquePointer typedefs?

I'm a little confused, is this about possible API incompatibility?

Also, if I understand this evolution proposal correctly, something similar was already implemented for Objective-C.

@hborla

• SE-0384: Importing Forward Declared Objective-C Interfaces and Protocols (ImportObjcForwardDeclarations)