<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 11, 2016, at 6:34 AM, David Hart <<a href="mailto:david@hartbit.com" class="">david@hartbit.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: HelveticaNeue; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">It sounds extreme to me to release a v1 of a library without giving yourself the flexibility to iterate on it beforehand.</span></div></blockquote></div><br class=""><div class="">Dispatch is already released (on two platforms). So that ship sailed in 2010. The question in front of us is whether we're going to focus in getting the Linux port to parity with Darwin or whether we're going off an an API design adventure before seriously addressing that goal.</div><div class=""><br class=""></div><div class="">It seems prudent to point out that "API design" appears <b class="">last</b> on our list of Swift 3 goals, while "<a href="https://github.com/apple/swift-evolution" class="">Portability</a>" is <b class="">in the top three</b>. So I don't know why my position would be "extreme", as it is more consistent with what we are on paper supposed to be doing in this release.</div><div class=""><br class=""></div><div class="">It also seems prudent to point out that we are going to do the first preview branch tomorrow. Obviously none of us really know what to expect, but the official guidance includes such statements as "only changes that align with the core goals of the release will be considered" and "Source-breaking changes to the language will be considered on a case-by-case basis." I think we should consider whether rewriting the entire Dispatch API surface area is something that would clear that bar.</div><div class=""><br class=""></div><div class="">I agree with all the individual API changes. They're great. I just think the timing is wrong. We should get to Darwin parity, and then we'll be in a position to pull the trigger on this.</div><div class=""><br class=""></div><div class="">Drew</div></body></html>