[swift-evolution] Enhancing access levels without breaking changes

Jose Cheyo Jimenez cheyo at masters3d.com
Mon Apr 10 12:34:10 CDT 2017

> On Apr 10, 2017, at 10:22 AM, Tino Heth <2th at gmx.de> wrote:
>>> I don't buy this argument at all without an objective explanation why the curly braces of extensions should be treated different than the curly braces of types…
>> Extensions are not Partials. 
>>> do you think sprinkling parts of class over the project is easier to follow?
>> Extensions are not Partials. 
> I can't see how statement and answer(?) are related to the original post… or did I miss that this topic is about partials? :)
I am partial to partials. :)
>>> it can be delayed for as long as the core team likes, without causing any trouble.
>> Partials limited to the same scope can do the same
> That is true… so can we agree that nothing should change now, so that something can be added later? ;-)
Same page. 
>> with out having to give extension special nesting powers :)
> I would say there's no doubt that extensions are withhold the common nesting powers of all other, similar constructs in Swift: Classes can be nested, Structs can be nested, Enums can be nested, functions can be nested, protocols… I haven't tried yet, but associated objects are something comparable ;-)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170410/962d0f17/attachment.html>

More information about the swift-evolution mailing list