[swift-evolution] [Post Swift 3] [Proposal] Introducing `group` mechanism

Jose Cheyo Jimenez cheyo at masters3d.com
Thu Jun 30 00:12:12 CDT 2016

You are being apprehensive about this. We all want grouping of access modifiers just like c++ has but what you are proposing doesn't seem to be a clear win. In fact I would much rather have plain c++ groupings than group{}.

Could you also "replay all" not just the evolution list? It makes it hard to follow threads. 

-1 from me as well, sorry. You should bring this additive change up again for discussion in August though. 

> On Jun 29, 2016, at 11:43 AM, Adrian Zubarev via swift-evolution <swift-evolution at swift.org> wrote:
> +1 what an argument! This doesn’t help here in any way.
> If you think there must be a solution for the problem you mentioned in your first reply here, feel free to propose for no more implicit access modifier.
> -- 
> Adrian Zubarev
> Sent with Airmail
> Am 29. Juni 2016 um 20:24:26, L. Mihalkovic (laurent.mihalkovic at gmail.com) schrieb:
>> If I recall, there was even a past argument from a core team member (chris?) about something different but alluding to a very similar lack-of-practicality-at-scale.
> _______________________________________________
> 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/20160629/2669d82c/attachment.html>

More information about the swift-evolution mailing list