[swift-evolution] [Proposal] Nested extensions

[Xiaodi Wu]

Sure:

One solution to the problem is to remove the use of access modifiers as a
shorthand in front of extensions. It was proposed, reviewed, and rejected:
https://github.com/apple/swift-evolution/blob/master/proposals/0119-extensions-access-modifiers.md

The discussion was here:
https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160711/024224.html

I tried to follow up with a much milder proposal to change the rules
surrounding access modifiers. It was discussed here:
https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160718/024588.html

The PR was here, but rejected for review by the core team:
https://github.com/apple/swift-evolution/pull/438/files


On Fri, Apr 14, 2017 at 1:04 PM, Tino Heth <2th at gmx.de> wrote:

>
> As I've mentioned three or four times already on this list, every time
> this issue is brought up, the rules of access modifiers as revised in
> SE-0025 *cannot accommodate* non-top level extensions.
>
> Sorry to bother you, but do you have a string to search for, or can
> forward a mail that's part of of one of those threads that haven't been
> allowed to be reviewed?
> Afair, there even was a review for a proposal that wanted to fully revert
> SE-0025, so I wonder why it should be forbidden to question parts of it?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170414/fe844c10/attachment.html>