[swift-evolution] Swift evolution proposal: introduce typeprivate access control level

Álvaro Monteiro alvarosilvamonteiro at gmail.com
Thu Dec 1 04:37:16 CST 2016


Very good idea because and it makes access control much more flexible.


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 at 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 <2th at 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 at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20161201/2bab0a3a/attachment.html>

More information about the swift-evolution mailing list