[swift-evolution] [swift-evolution-announce] [Review] SE-0088: Modernize libdispatch for Swift 3 naming conventions
drew at sealedabstract.com
Wed May 11 06:58:34 CDT 2016
> On May 11, 2016, at 6:34 AM, David Hart <david at hartbit.com> wrote:
> It sounds extreme to me to release a v1 of a library without giving yourself the flexibility to iterate on it beforehand.
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.
It seems prudent to point out that "API design" appears last on our list of Swift 3 goals, while "Portability <https://github.com/apple/swift-evolution>" is in the top three. 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.
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.
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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution