[swift-evolution] Revisiting SE-0110

Gwendal Roué gwendal.roue at gmail.com
Tue Jun 6 10:32:05 CDT 2017


> Le 6 juin 2017 à 17:22, Shawn Erickson <shawnce at gmail.com> a écrit :
> 
> 
> 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

You are right, Shawn. I hope that the core team is currently enjoying all the congratulations they deserve :-)

Gwendal

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170606/2a964968/attachment.html>


More information about the swift-evolution mailing list