Does the Swift 3.0 compatibility mode refer to 3.0.1 or just 3.0? The lack of dynamic bridging of NSNumber and NSValue in 3.0 might cause some Darwin projects to pass compilation but fail in tests.
Regards, Anders > On 25 Apr 2017, at 5:55 AM, Nicole Jacque via swift-evolution > <swift-evolut...@swift.org> wrote: > > Hello Everyone- > > I am happy to announce the release of a new Swift Source Compatibility Suite > on ci.swift.org! This suite supports testing for the goal of maintaining > source compatibility for future Swift releases. The suite will periodically > (and via pull request testing) build projects included in the suite against > development versions of Swift in order to catch source compatibility > regressions as early as possible. While we have seeded the suite with a few > initial projects, the content of the suite will be community driven, and I > encourage everyone to add projects to the suite to help improve the breadth > of testing. We’d love to see a robust suite with thousands of test projects! > A list of currently included projects and details for how to add projects > can be found here: > https://swift.org/source-compatibility/ > > Pull request testing will also be available in order for you to verify the > source compatibility of your changes before merging. The syntax for > requesting pull request testing is: > @swift-ci Please Test Source Compatibility > > You can view all source compatibility jobs at: > https://ci.swift.org/view/Source%20Compatibility/ > > Thanks! > nicole > > _______________________________________________ > swift-evolution mailing list > swift-evolut...@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
