[swift-evolution] Revisiting SE-0110

Gwendal Roué gwendal.roue at gmail.com
Sat May 27 07:23:43 CDT 2017

> Le 27 mai 2017 à 14:20, Gwendal Roué <gwendal.roue at gmail.com> a écrit :
>> Le 26 mai 2017 à 21:35, Robert Bennett via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> a écrit :
>> On the contrary I think the solution can absolutely be to break other code. 
> You can break whatever you want.
> But whatever the solution you come up with, remember that SE-0110 currently *degrades* the quality of code written by Swift programmers. It can be argued that SE-0110 is a blatant *regression*. Maybe not as bad as the initial introduction of fileprivate, but something which is pretty bad, though.
> References:
> - https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170522/036808.html <https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170522/036808.html>
> - https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170522/036814.html <https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170522/036814.html>
One more link, about the loss of single-lign closures induced by SE-0110: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170522/036792.html


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170527/49c0a015/attachment.html>

More information about the swift-evolution mailing list