[swift-evolution] Revisiting SE-0110

Ray Fix rayfix at gmail.com
Tue Jun 6 10:42:21 CDT 2017

FWIW, after doing a project migration last night and this morning, I am reluctantly +1 for reverting SE-0110 and seeing a new proposal that can be properly evaluated.  The split-the-difference compromise mentioned seems like just that, a compromise that will need to be revisited anyway.

While I agreed with the spirit of the original proposal, the assertion that "Minor changes to user code may be required if this proposal is accepted.” seems like it underestimated the magnitude of the impact. In almost every case, my code lost clarity.

Other aspects of the migration went quite smoothly.

BTW, if I were at WWDC this year I would be in the Swift lab pestering them about this.  Hopefully that feedback is happening. :)


> On Jun 6, 2017, at 8:22 AM, Shawn Erickson via swift-evolution <swift-evolution at swift.org> wrote:
> On Tue, Jun 6, 2017 at 7:18 AM Gwendal Roué via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> Le 6 juin 2017 à 15:30, Vladimir.S <svabox at gmail.com <mailto:svabox at gmail.com>> a écrit :
>> I'm just trying to understand your opinion.
>> Let me know, what result do you *expect* for this Swift4 code given what SE-0066 requires for function types:
>> func foo(x : (Int, Int))->() {}
>> print(type(of: foo))  // ??
>> print(foo is (_: Int, _: Int)->())  // ??
> I couldn't care less.
> What I care about: the code regressions introduced by SE-0110 (look at previous messages in this long thread, and the ridiculous state of closures that eat tuples), and the migration bugs (look at Xcode 9 release notes).
> Note that many of Apple's swift team are likely swamped with WWDC at the moment. They are also dealing with merging out their private changes announced so far at WWDC. Xcode 9 is prerelease still so expect things to get revised to some degree before the final release.
> Not say to not voice concerns but at this time some patience will be needed.
> -Shawn
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170606/32766029/attachment.html>

More information about the swift-evolution mailing list