> On 4 Apr 2017, at 10:01, David Waite via swift-evolution > <[email protected]> wrote: > > I believe we can leave the option open of widening private later as part of a > tasked redesign of access control after Swift 4.0. I’d prefer to not widen > private before we have evaluated access control as a whole, as I believe > private as it is today is the lowest, most restrictive-but-usable level of > access control.
Can we get a clear answer from the core team as to whether a redesign of access control is going to be permitted post Swift 4.0? There are a few replies in this thread that are insinuating that no further changes will be permitted. -Tony ---------- Tony Arnold +61 411 268 532 http://thecocoabots.com/ ABN: 14831833541 _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
