I still say that this is the case where we do take a stand and do ask for this proposal to be blocked and re-analised, I cannot believe that we are going to be addingthis kind of incosistency to the language and take readability/ease of local reasoning (which Apple stressed at the last WWDC once again) away. The community and the core team just finished bikeshedding a huge change to how API's are imported and how labels are used and how important they are and then we do this?
On Fri, Jul 8, 2016 at 10:22 AM, Tino Heth via swift-evolution < [email protected]> wrote: > > Aw. It's really bad that labels are gone for closures at the call site 😢. > IMHO, the same principles that encourage the use of labels for "normal" > function calls should prevail here. > > No need to feel bad — if I wasn't ignored (it's hard to notice if this > happens ;-), the argument has been considered. > > Additionally, those labels may return in the future — although there is a > astoundingly long list of features that will be removed because their > implementation is flawed, and whose fans have been calmed down with the > argument that they'll be re-added in an improved form later ;-) > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution > >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
