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

Goffredo Marocchi panajev at gmail.com
Fri Dec 2 13:51:17 CST 2016

 is a POP language right? So lets focus on fixing and improving protocols. :) We should start with open/public protocol.
No, this is not a POP language only, OOP is neither discourage nor unwelcome and it is a first class citizen. 
Telling people there are better ways in some / many scenarios and that deep inheritance hierarchies are bad is not the same thing: composition as spatter was not born with Swift.

I do not want to offend, but it is getting a bit irritating that whenever someone wants to improve object oriented patterns the answer resembles a "why bother? Isn't it an unsupported feature anyway?" :P.

People want to improve POP patterns? Good, it does not and should not upset or come at the expenses of other first class features... everybody is happy then... almost :).

> PS: I also cannot wait for existentials to drop typealias ProtoB = Any<Proto> where Proto.A == B where B comes from a generic parameter list and A is an associated type.
> -- 
> Adrian Zubarev
> Sent with Airmail
> Am 2. Dezember 2016 um 12:36:45, Gonçalo Alvarez Peixoto (goncalo.alvarezpeixoto at gmail.com) schrieb:
>> Also, would you be so kind to provide an example where typepublic would be useful? Maybe you're thinking of allowing member access to subclasses? Would that fall into a possible "protected" realm?
> _______________________________________________
> 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/20161202/137c2c22/attachment.html>

More information about the swift-evolution mailing list