<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi Brian!<br><br></div><div><br>On Jun 14, 2016, at 10:43 AM, Brian Gesiak <<a href="mailto:modocache@gmail.com">modocache@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">Excellent work! I've been enjoying watching all the WWDC livestreams. :)</div></div></blockquote><div><br></div>Thanks! We have a few more sessions coming up that are pretty neat too. <div><br><blockquote type="cite"><div><div dir="ltr"><div><br></div><div>About the changes to swift-corelibs-xctest: you mean simply using the new Foundation APIs, correct? I don't imagine we'll be changing the XCTest API very much -- that is, we won't be renaming `XCTestCase` to `TestCase`, right?</div></div></div></blockquote><div><br></div>Yup, exactly. Some of the name changes have landed in swift-corelibs-foundation already, and there have been corresponding PRs to fix our clients. This will be more of the same types of fixes.</div><div><br></div><div>- Tony</div><div><br><blockquote type="cite"><div><div dir="ltr"><div><br></div><div>We discussed this [in Feburary](<a href="https://lists.swift.org/pipermail/swift-corelibs-dev/Week-of-Mon-20160222/000446.html">https://lists.swift.org/pipermail/swift-corelibs-dev/Week-of-Mon-20160222/000446.html</a>), and I believe the conclusion was that we wouldn't be applying the same kinds of grand renaming to XCTest -- would just like to confirm that point.</div><div><br></div><div>- Brian Gesiak</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 14, 2016 at 1:24 PM, Tony Parker via swift-corelibs-dev <span dir="ltr"><<a href="mailto:swift-corelibs-dev@swift.org" target="_blank">swift-corelibs-dev@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hello everyone,<div><br></div><div><div>If you’ve downloaded Xcode 8 beta 1, you’ve seen some of the great changes we’ve got coming up for Swift 3 on Darwin. We have been working in parallel on those improvements and the changes that we need to bring swift-corelibs-foundation up-to-date, including:</div><div><br></div><div> * new value types (SE-0069)</div><div> * new names for API and NS-dropping changes (SE-0086)</div><div><div> * new tests (mostly part of the overlay, not all merged to corelibs yet)</div></div><div><br></div><div>We plan to post later today a branch (<i>name forthcoming) </i>to the swift-corelibs-foundation repository that contains the first version of all of these changes. We’ve also been merging all of the other changes from master branch.</div><div><br></div><div>It’s not quite ready to merge back to master yet, so we would appreciate your help! Check out the branch, look for errors or omissions, and submit some PRs or send mail to this list.</div><div><br></div><div>Our hope is to merge this branch very quickly, in the span of a week or two at most. We will likely need to get some parallel PRs up for XCTest and swiftpm to help them adapt to the new name and type changes. </div><div><br></div><div>Thanks!</div><span class="HOEnZb"><font color="#888888"><div>- Tony</div><div><br></div></font></span></div></div><br>_______________________________________________<br>
swift-corelibs-dev mailing list<br>
<a href="mailto:swift-corelibs-dev@swift.org">swift-corelibs-dev@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-corelibs-dev" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev</a><br>
<br></blockquote></div><br></div>
</div></blockquote></div></body></html>