> The current rules in SE-0025 state that the access modifier in front of the > extension states both the default and the maximum allowed visibility. This is > what I was trying to change. Oh dear! But afaics, SE-0025 is not to blame for all those complications, and many problems have a different origin… did you encounter any serious counter arguments to reduce the rules for access modifiers on extensions to "it sets the default for all entities contained in the extension"? I think I'll do a PR despite those issues — changing the rules to allow nesting wasn't accepted, but maybe introduce nesting to change the rules works out ;-) _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
Re: [swift-evolution] [Proposal] Nested extensions
Tino Heth via swift-evolution Sat, 15 Apr 2017 23:04:23 -0700
- Re: [swift-evolution] [Proposal] Nested exte... Xiaodi Wu via swift-evolution
- Re: [swift-evolution] [Proposal] Nested... Tino Heth via swift-evolution
- Re: [swift-evolution] [Proposal] Ne... Xiaodi Wu via swift-evolution
- Re: [swift-evolution] [Proposal... Tino Heth via swift-evolution
- Re: [swift-evolution] [Prop... Xiaodi Wu via swift-evolution
- Re: [swift-evolution] ... Tino Heth via swift-evolution
- Re: [swift-evoluti... Xiaodi Wu via swift-evolution
- Re: [swift-evoluti... Tino Heth via swift-evolution
- Re: [swift-evoluti... Xiaodi Wu via swift-evolution
- Re: [swift-evoluti... Xiaodi Wu via swift-evolution
- Re: [swift-evoluti... Tino Heth via swift-evolution