<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="margin: 0px;"><div style="color: rgb(0, 0, 0); font-family: Helvetica, Arial; font-size: 13px;"><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><blockquote type="cite" class=""><div class="">On May 20, 2016, at 10:54 AM, Adrian Zubarev via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div id="bloop_customfont" class="" style="font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; margin: 0px;">Can submodules enforce the developer to use its name ’Submodule.SomeClass’?</div></div></blockquote><div><br class=""></div><div>Ideally we would have flexible import syntax that allows for control over *how* names are imported into a lexical context (including the ability to import names within a very specific scope if desired).</div></div></blockquote></div><p style="color: rgb(0, 0, 0); font-family: Helvetica, Arial; font-size: 13px;">Ok fine.</p><div><div style="color: rgb(0, 0, 0); font-family: Helvetica, Arial; font-size: 13px;"><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><blockquote type="cite" class=""><div class=""><div id="bloop_customfont" class="" style="font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; margin: 0px;">Do I have to re-build submodules when I made any changes to them before building the outside code base?</div></div></blockquote><div><br class=""></div><div>All <b class="">sub</b>modules are part of the same target as the module that contains them.</div><br class=""><blockquote type="cite" class=""><div class=""><div id="bloop_customfont" class="" style="font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; margin: 0px;">Can they efficiently used for cross decencies between different modules/submodules?</div></div></blockquote><div><br class=""></div><div>Cross decencies? I don’t understand.</div></div></blockquote></div><p>Sorry it’s me again: "<span style="color: rgb(0, 0, 0); font-family: 'helvetica Neue', helvetica; font-size: 13px;">cross dependencies</span><font face="helvetica Neue, helvetica">“</font></p><p style="color: rgb(0, 0, 0); font-size: 13px;">MainProject (module/package)</p><div> |__Submodule</div><div> | |__SubSubmodule</div><div> |__AnotherSubmodule</div><div><br></div><div>Can I enforce usage of `AnotherSubmodule.Someclass` inside of `SubSubmodule`???</div><div style="color: rgb(0, 0, 0); font-family: Helvetica, Arial; font-size: 13px;"><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><blockquote type="cite" class=""><div class=""><div id="bloop_customfont" class="" style="font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; margin: 0px;">Empty enums is an abuse of the language! </div></div></blockquote><div><br class=""></div><div>But it is a practical and effective one. Introducing a new construct like namespaces must carry significant advantages over what is already possible.</div></div></blockquote><br class="Apple-interchange-newline"></div>Still abuse of the language no matter how you turn it. I don’t say `namespaces` should only do the same enums do (in my case it would be enough), if there is more they could solve sure why not. Thats a discussion is for isn’t it? I’m not an expert so I want to learn from people that might provide good examples and reasons why namespaces are good or not. </div><div style="color: rgb(0, 0, 0); font-family: Helvetica, Arial; font-size: 13px;"><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br></div></div></div></div><div><div> <div id="bloop_sign_1463760520844299008" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Adrian Zubarev<br>Sent with Airmail</div></div><blockquote type="cite" class="clean_bq"><span><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div></div></div></span></blockquote></div></div></body></html>