<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=""><div class="">I personally dislike the habit of deliberately naming different classes using the same name within a single project/module/library, just using different namespaces - one should be able to deduct from the code *which* class is being used without excessive checking.</div><div class=""><br class=""></div><div class="">When you have namespaces Car and Animal and each contains a class called List, IMHO there should be classes CarList and AnimalList. It's more verbose, but you imediately know which class is being used in opposite of just using List.</div><div class=""><br class=""></div><div class="">I don't have much experience with C++ and C#, but sometimes I have to dive into C# code and you can hear my teeth grind since there is a declaration of a variable of class List and you have no idea which List is this, since there are dozens of classes with this name. You don't always have the code in an IDE to resolve the symbol for you, sometimes you browse it on git, etc.</div><div class=""><br class=""></div><div class="">Which is why I personally find modules sufficient in providing a way to prevent naming collisions, yet strict enough to discourage the habits of other languages described above.</div><div class=""><br class=""></div><div class="">Hence for me -1 on introducing multiple namespaces within a single module.</div><br class=""><div><blockquote type="cite" class=""><div class="">On May 20, 2016, at 3:27 PM, Leonardo Pessoa 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 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;" class=""><div style="font-family: Calibri, sans-serif; font-size: 11pt;" class="">Adrian, I myself don't see a reason other than "Objective-C never had it so why bother about it now?" Most (if not all) .net languages support optional namespaces and even PHP began supporting it in version 5 (if I'm not sure if the version is right). No technical reason against and I'm particularly in favour too so let's hear the others in the group.</div></div><div dir="ltr" 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;" class=""><hr class=""><span style="font-family: Calibri, sans-serif; font-size: 11pt; font-weight: bold;" class="">From:<span class="Apple-converted-space"> </span></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;" class=""><a href="mailto:swift-evolution@swift.org" class="">Adrian Zubarev via swift-evolution</a></span><br class=""><span style="font-family: Calibri, sans-serif; font-size: 11pt; font-weight: bold;" class="">Sent:<span class="Apple-converted-space"> </span></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;" class="">20/05/2016 09:16 AM</span><br class=""><span style="font-family: Calibri, sans-serif; font-size: 11pt; font-weight: bold;" class="">To:<span class="Apple-converted-space"> </span></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;" class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a></span><br class=""><span style="font-family: Calibri, sans-serif; font-size: 11pt; font-weight: bold;" class="">Subject:<span class="Apple-converted-space"> </span></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;" class="">[swift-evolution] [Discussion] Namespaces</span><br class=""><br class=""></div><div id="bloop_customfont" 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; margin: 0px;" class="">I want to revive this topic.</div><div id="bloop_customfont" 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; margin: 0px;" class=""><br class=""></div><div id="bloop_customfont" 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; margin: 0px;" class="">Is there any technical reason why we can’t have namespaces in Swift? I’ve found just a few threads about namespaces, but most of them had arguments to use modules instead.</div><div id="bloop_customfont" 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; margin: 0px;" class=""><br class=""></div><div id="bloop_customfont" 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; margin: 0px;" class="">I’m fine with modules but they just don’t serve everything I would want to. I can’t enforce the developer to use the modules name if there is no naming conflict.</div><div id="bloop_customfont" 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; margin: 0px;" class=""><br class=""></div><div id="bloop_customfont" 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; margin: 0px;" class="">I asked in the SwiftPM mail list for a easier Xcode integration of modules, but the response is exactly the opposite for using modules for namespaces (read below).</div><div id="bloop_customfont" 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; margin: 0px;" class=""><br class=""></div><div id="bloop_customfont" 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; margin: 0px;" class="">If I’m building one huge project I don’t want to build a lot of different modules just shiny namespaces and clean code.</div><div id="bloop_customfont" 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; margin: 0px;" class=""><br class=""></div><div id="bloop_customfont" 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; margin: 0px;" class="">So I ask the community again why can’t we have optional namespaces?</div><div class="bloop_sign" id="bloop_sign_1463745513731555072" 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 style="font-family: helvetica, arial; font-size: 13px;" class="">-- <br class="">Adrian Zubarev<br class="">Sent with Airmail</div></div><br 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;" class=""><p class="airmail_on" 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;">Am 19. Mai 2016 bei 22:33:19, Daniel Dunbar (<a href="mailto:daniel_dunbar@apple.com" class="">daniel_dunbar@apple.com</a>) schrieb:</p><blockquote class="clean_bq" type="cite" 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;"><span class=""><div style="-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""></div><div class=""><div class="">Right now modules are most appropriately used at the same granularity that frameworks or shared libraries would be used in C/Obj-C/C++. This is the situation for which the variety of access control modifiers in Swift and things like Whole Module Optimization were designed for. While there are a lot of reasons to like modules as a way to provide namespaces, they really haven't been designed to provide these very fine grained namespaces.</div><div class=""><br class=""></div><div class="">My guess is that the right answer here doesn't really involve the Xcode integration, but rather figuring out the right way that these concepts fit into the language in a first class way. I would expect concepts like submodules or namespaces to be language concepts that Xcode just exposes, not something that was coupled together.</div><div class=""><br class=""></div><div class=""> - Daniel</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On May 18, 2016, at 12:37 PM, Adrian Zubarev via swift-build-dev <<a href="mailto:swift-build-dev@swift.org" class="">swift-build-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><h1 style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: -webkit-standard; font-style: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica, Arial; font-size: 13px; font-weight: normal;" class="">I’d like to discuss an idea that will make development in Xcode easier. I assume that SwiftPM will see its Xcode integration when the final version will be released.</span></h1><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">Problem I’ll try to describe is mostly about namespaces. Right now some people abuses enums, struct or classes to create a namespace for a specific need.</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">class Reference {</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""> class String { … }</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""> class Character {</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""> enum Error { … }</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""> }</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""> private init() {}</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">}</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">This will create a pseudo namespace for the nested types:</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">* Reference.String</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">* Reference.Character</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">* Reference.Character.Error</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">One could argue of using modules instead of abusing a class here, which is a great argument.</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">The problem that comes to my mind here is that we will have to create subprojects inside our main project file and using the references to them just to achieve that shiny namespace.</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">One could also use SwiftPM, which is awesome, but there is a need to re-build the module if any changes have been done. As soon as we’ll create some complex dependencies between different modules this will get messy.</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">Before posting here I asked Joe Groff if there is any mailing list I can use to discuss my idea. He told me this might be a good place, because I was referring to the package manager. Then I’ve done my research to not create any redundant thread, but I only found one topic about the integration of SwiftPM in Xcode:<span class="Apple-converted-space"> </span><a href="https://lists.swift.org/pipermail/swift-build-dev/Week-of-Mon-20160215/000272.html" class="">https://lists.swift.org/pipermail/swift-build-dev/Week-of-Mon-20160215/000272.html</a></div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">So here are my thoughts about a deeper integration of SwiftPM here:</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">- What if Xcode will introduce two new types of groups (the folder color could be orange like Swift for example, or even contain the bird icon).</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">- These groups are analogous to already existing group types except they’ll represent Swift modules / packages</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">- Basically we’ll have a single project file with multiple modules, where these modules should only exist inside that project (this is my own need right now)</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">- Such a package / module group will have a configurable utilities, where one could configure the modules</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">- This will reduce the re-building process, allow us to keep everything (not only .a or we’ll be able to hide .a files and just keep the sourcefiles inside such groups) inside a single project,<span class="Apple-converted-space"> </span><b class="">gain the shiny namespaces like above</b>, and make the file management way easier </div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">- This also should allow us create cross-dependencies if there is a good need for that in our project</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">+ MainProject</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">|</div><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px;" class="">+—Reference (module)</div></div></blockquote></div></div></div></div></span></blockquote><br 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;" class=""><div 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;" class="">[The entire original message is not included.]</div><span 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; float: none; display: inline !important;" class="">_______________________________________________</span><br 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;" class=""><span 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; float: none; display: inline !important;" class="">swift-evolution mailing list</span><br 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;" class=""><a href="mailto:swift-evolution@swift.org" 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;" class="">swift-evolution@swift.org</a><br 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;" class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" 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;" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a></div></blockquote></div><br class=""></body></html>