[swift-evolution] Swift evolution proposal: introduce typeprivate access control level
Gonçalo Alvarez Peixoto
goncalo.alvarezpeixoto at gmail.com
Tue Nov 29 10:07:20 CST 2016
Thanks for your feedback.
However, I tend to disagree with you.
*"The proposal, as it stands, does nothing to indicate how this is much
different from internal - all examples given would trivially be solved by
This proposal aims at covering all of the cases in which you *do not want* to
expose your properties *internally. *For instance, you might want to access
a member of a view controller from an extension of this view controller on
another file, but not make it accessible from other members in the
module (which is what *internal *does).
2016-11-29 15:53 GMT+00:00 Robert Widmann <devteam.codafi at gmail.com>:
> The proposal, as it stands, does nothing to indicate how this is much
> different from internal - all examples given would trivially be solved by
> internal members. I don’t think we need finer-grained access control to
> address this, I think we need extensions, at least in the same file as
> their parent declarations, to be able to define variables.
> On Nov 29, 2016, at 10:24 AM, Gonçalo Alvarez Peixoto via swift-evolution <
> swift-evolution at swift.org> wrote:
> Hello, everyone!
> I would like to introduce a new proposal to swift evolution, but first I
> would love to run it by all of you so I get everyone's feedback and enrich
> This proposal consists of introducing a new *typeprivate *access control
> level which allows for members to be accessed in all extensions of a given
> *type,* whether lying within or in another file.
> You'll find the proposal draft in:
> Thanks in advance for taking the time to evaluate the proposal.
> Best regards,
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution