@Daniel: Very good idea because and it makes access control much more flexible.
@Tino: Couldn't agree with you more about the usage of "swifty". I think it's applicable here because communication is something that everyone agrees is a essential in swift and access control is one of the many ways developers have to properly describe (and communicate) an API. On Thu, Dec 1, 2016 at 10:22 AM, João David via swift-evolution < swift-evolution@swift.org> wrote: > Exactly. Totally agree Tino. > > Sent from my iPhone. Erroneous words are a feature, not a typo. > > On 1 Dec 2016, at 09:31, Tino Heth <2...@gmx.de> wrote: > > > It also means that anybody who want to access your private var will just > have to write an extension to expose it. > > imho this is wrong thinking: > Access control is no tool to offer real "protection" — it can't stop > someone who wants to break a system. > Especially in the world of open source, it is merely an advice from the > author not to do certain things. > > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution > >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution