>Swift 2.2 code should be run through a migrator, which is able to automatically handle changes like this.
Yes, but that's not really my point. Why do it this "magical" way? It's already possible (and actually very easy) to wrap C modules such as libdispatch in a Swifty API (see Venice <https://github.com/VeniceX/Venice>, OpenSSL <https://github.com/Zewo/OpenSSL>, PostreSQL <https://github.com/Zewo/PostgreSQL> as examples). I know that LibDispatch is special to Swift and Apple, but I just don't see a reason to give it such a special treatment. Dan On Thu, May 19, 2016 at 9:56 PM Chris Lattner <[email protected]> wrote: > > > On May 19, 2016, at 9:53 PM, Dan Appel <[email protected]> wrote: > > > > Does this mean that all current code using Dispatch is broken? > > Are you asking about Swift 2.2 code? > > Swift 2.2 code is generally completely incompatible with Swift 3 for a lot > of other reasons (e.g. major changes to the standard library APIs). Swift > 2.2 code should be run through a migrator, which is able to automatically > handle changes like this. > > -Chris -- Dan Appel
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
