> Le 26 mai 2017 à 21:35, Robert Bennett via swift-evolution > <swift-evolution@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> It would be nice if some responsible language designer would at least *agree* that there is a problem. Gwendal Roué
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
