<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Before bringing this forward, I’ve tried brackets { } as well <div class="">for “my feature” but found this to be a bit awkward, </div><div class="">confusing with real program { } blocks, </div><div class="">also because it has nothing to do with blocks</div><div class="">(except for the class or struct body as limitation) </div><div class="">rather its effect is sequential, line by line, </div><div class="">within the class or struct body.<div class="">e.g:</div><div class=""> default scope here.</div><div class=""> private:</div><div class=""> source lines</div><div class=""> all declarations in lines following are private</div><div class=""> until another in-line scope designator is encountered.</div><div class=""> defalutscope:</div><div class=""> source lines</div><div class=""> public:</div><div class=""> source lines</div><div class=""> end of class/ struct/ </div><div class=""><br class=""></div><div class="">Thus, it acts more or less like a compiler directive… </div><div class="">therefore, perhaps this would better: </div><div class=""><br class=""></div><div class="">@private:</div><div class=""> source lines</div><div class="">@public:</div><div class=""> source lines</div><div class="">@defaultscope: // returns to default scope </div><div class=""> source lines.</div><div class=""> </div><div class="">?</div><div class=""><br class=""></div><div class="">TedvG</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 20. Jun 2017, at 18:32, Tino Heth <<a href="mailto:2th@gmx.de" class="">2th@gmx.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""><blockquote type="cite" class=""><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">You can already effectively have these "regions" using extensions, with the exception of stored properties since they can't be placed there.</span></div></blockquote></div>I still think nested extensions would have been a good addition to the language: If we had those, <div class=""><br class=""></div><div class="">struct MyType {</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>private {</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>var myPrivateVar: Int?</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>var anotherOne: String?</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>}</div><div class="">}</div><div class=""><br class=""></div><div class="">would be a rather small piece of syntactic sugar...</div></div></div></blockquote></div><br class=""></div></div></body></html>