<html><body><div>I think there are some rough edges here that could be refined, but as a long time Obj-C guy, I'm fine leaving prefixes behind. They've frequently been misused. Third parties are supposed to use three letter prefixes, but frequently only use two, increasing the chances of a collision. Name prefixes to me have seemed like a ticking time bomb. I have nightmares about us or a dependency colliding with Apple's prefixes in an OS update, especially now that I've seen a few three letter prefixes coming from Apple.</div><div><br data-mce-bogus="1"></div><div>I also don't think prefixes fit well with Swift Foundation, and Swift Foundation shouldn't diverge that significantly from Apple Foundation.</div><div><br data-mce-bogus="1"></div><div>I think there are several ways of dealing with the issues raised here:</div><div>- Promote defining variables by their fully quantified type names. I wasn't even sure that I could do Foundation.NSString until I tried it just now.</div><div>- Keep the hierarchies small. What always drives me crazy in languages like Java (and that C# example) is the huge hierarchies. We should probably strive to keep things simple. Foundation.String, not System.Utils.Foundation.Text.String.</div><div><br data-mce-bogus="1"></div><div>Something like CoreImage.Image and AppKit.Image is a little more bulky, but I think it actually reads better.</div><div><br data-mce-bogus="1"></div><div>I don't have strong opinions on selectively importing portions of modules. But if that was to be promoted as a development methodology, I'd like Xcode to automatically manage my imports, much like Eclipse and Android Studio do. When I umbrella import a module, I typically do so out of laziness, so having the IDE take care of my imports for me is a nice compromise.</div><div><br>On Feb 01, 2016, at 10:21 AM, Drew Crawford via swift-evolution <swift-evolution@swift.org> wrote:<br><br></div><div><blockquote type="cite"><div class="msg-quote" style="word-wrap: break-word;" data-mce-style="word-wrap: break-word;">I am in favor of this proposal on balance, and I leave the bulk of this to people who interop with Objective-C more often than I do.<div class=""><br class=""></div><div class="">I would like to confine my remarks to one corner where I think we are making a very serious mistake.</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class="">The removal of the "NS" prefix for the Foundation module (or other specifically identified modules) is a mechanical translation for all global symbols defined within that module that can be performed in the Clang importer. </blockquote></div><div class=""><br class=""></div><div class="">As I understand it (and I am no Cocoa historian) the NS prefix was originally introduced because Objective-C lacks namespacing.</div><div class=""><br class=""></div><div class="">The thinking seems to be that since Swift has proper namespacing, this historicism is no longer necessary. I find this argument very flimsy.</div><div class=""><br class=""></div><div class="">Of course Swift has stronger namespacing if one's frame of reference is Objective-C or C. But for those of us coming from other language backgrounds, namespacing means something much stronger than Swift's concept of it. I don't mean to suggest that Swift's design is wrong exactly (less is sometimes more), but I do mean to say that if we propose to undo a decision that worked for several decades and break every Swift project in existence on the theory that Swift's namespacing is strong enough we had better be right.</div><div class=""><br class=""></div><div class="">For those unfamiliar, I will explain some of the namespacing tools Swift lacks relative to other languages. First, many languages have a "hierarchical" namespace system, where one can say</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="" data-mce-style="margin: 0 0 0 40px; border: none; padding: 0px;"><div class="">import <a href="http://Foundation.Net" data-mce-href="http://Foundation.Net">Foundation.Net</a>.URL</div><div class="">let s = Session(...)</div></blockquote><div class=""><br class=""></div>instead of for example<div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="" data-mce-style="margin: 0 0 0 40px; border: none; padding: 0px;"><div class="">import Foundation</div><div class="">let s = NSURLSession(...)</div></blockquote><br class=""><div class=""><div class="">Some form of this is used in Rust, Python, and C#, as far as I know. I believe Swift has some counterfeit version of this, as the book mentions you can import a "<a href="https://developer.apple.com/library/ios/documentation/Swift/Conceptual/Swift_Programming_Language/Declarations.html#//apple_ref/swift/grammar/import-declaration" class="" data-mce-href="https://developer.apple.com/library/ios/documentation/Swift/Conceptual/Swift_Programming_Language/Declarations.html#//apple_ref/swift/grammar/import-declaration">submodule</a>", but I do not know what that is, do not know how to make one, have never seen anyone use one, the book suggests it goes only 2 levels deep, and perhaps as a consequences of some of these problems nobody thought of using this for Foundation.</div><div class=""><br class=""></div><div class="">A closely related difference is the use of so-called "selective" imports, where we import only a single symbol (or a list of explicitly-identified symbols) into the scope. We might express this as</div><div class=""><br class=""></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="" data-mce-style="margin: 0 0 0 40px; border: none; padding: 0px;"><div class=""><div class=""><div class="">from <a href="http://Foundation.Net" data-mce-href="http://Foundation.Net">Foundation.Net</a>.URL import Session, HTTP //import two classes only</div></div></div><div class=""><div class=""><div class="">let s = Session(...)</div></div></div></blockquote><div class=""><br class=""></div>Again I think Swift technically supports some way to avoid importing a whole gigantic namespace like Foundation, but I am not aware of any actual uses of this feature, and certainly the convention is not to write code this way. Meanwhile, let's check in with the Python community, who standardized the following guidance on these "wildcard" imports as part of their language evolution process:<div class=""><br class=""></div><div class=""><blockquote type="cite" class="">Wildcard imports ( from <module> import * ) should be avoided, as they make it unclear which names are present in the namespace, confusing both readers and many automated tools. There is one defensible use case for a wildcard import...</blockquote><div class=""><div class=""><br class=""></div><div class="">When a language has a robust namespacing system, which we do not, there are many follow-on consequences. One is that an import statement is much more of a scalpel than a bludgeon; each import statement only introduces a handful of new names (even if it is a so-called "wildcard" import that grabs all children of some namespace, most of those children are themselves namespaces), unlike importing Foundation which contains thousands of direct child types that are injected into the local scope.</div><div class=""><br class=""></div><div class="">Another consequence is that class names become quite short, shadow each other, and nobody bats an eye. I searched the C# standard library for "Session", and found some 12 classes with that name:</div><div class=""><br class=""></div><div class=""><img id="80A643B8-C5DC-46B5-AB2B-1847214B57D0" height="245" width="585" src="cid:d79247aa-0fd3-4d27-ba77-da6bc587727c@icloud.com" class="" data-inline-image="true" data-mce-src="cid:d79247aa-0fd3-4d27-ba77-da6bc587727c@icloud.com" ></div><div class=""><br class=""></div><div class="">These "standard library" classes not only potentially shadow programmer-defined types, <b class="">they also shadow each other</b>. But because the C# language has a robust namespacing system, the chances of there being more than one thing called "Session" in scope in your program (or for that matter, when developing the standard library itself) is quite small, so it's a non-issue.</div><div class=""><br class=""></div><div class="">Now we return to the question of dropping the NS prefix, which will rename thousands of classes in a typical program that has `import Foundation`, in a way that potentially (let's be honest. More like "probably") shadows one or more programmer-defined classes. Our review criteria is:</div><div class=""><br class=""></div><div class=""><div class=""><blockquote type="cite" class="">Is the problem being addressed significant enough to warrant a change to Swift?</blockquote></div></div><div class=""><br class=""></div><div class="">No, the elimination of 2 characters is not significant enough of a problem to break all Swift programs, let alone to introduce literally thousands of new opportunities for shadowing.</div><div class=""><br class=""></div><div class="">To its credit, the proposal acknowledges this, and offers a concession:</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class="">Note that this removal can create conflicts with the standard library. For example, NSString and NSArray will become String and Array, respectively, and Foundation's versions will shadow the standard library's versions. In cases where the Swift 3 names of standard library entities conflict with prefix-stripped Foundation entities, we retain the NS prefix. These Foundation entities are: NSArray, NSDictionary, NSInteger, NSRange, NSSet, and NSString.</blockquote><br class=""></div><div class="">But of course this needlessly draws a distinction between NSString et al and the "normal" Foundation types, and what's more it draws that distinction based on the present composition of the Swift standard library and the present composition of Foundation. But we have already decided not to guarantee the source compatibility of the standard library, so what happens when that composition changes? Will we then go back and tweak which classes get NS prefixed to them again?</div><div class=""><br class=""></div><div class="">In my view, if Swift's namespacing is not good enough to let us drop the NS in NSString it is not good enough to drop any prefix. If we believe that a programmer will struggle to distinguish between Swift String and Foundation String then we should expect them to struggle for any two classes in any two frameworks, and this is special pleading on the part of Foundation. C#'s libraries declare *<b class="">twelve</b>* different `Session`s and nobody bats an eye, but we have two types share a name and everybody loses their minds? Our namespacing is not good enough to kill the prefix, period.</div><div class=""><br class=""></div><div class="">We should either drop these prefixes or we should not; because the claimed motivation–that we have "good enough" namespacing in the language now–is either true or it is not. This proposal admits that it is not, and tries to drop the prefixes anyway. I believe that is a mistake.</div><div class=""><br class=""></div><div class="">I certainly support the goal of eliminating these prefixes, they are ugly, they need to be killed, and namespacing is the right solution. But we must not jump out of the plane until we are very sure our parachute is in order. In Swift 3 it is not.</div><div class=""><br class=""></div><div class="">I do think the bulk of the proposal is fine, and I apologize for using quite stark language for such a small paragraph in an otherwise reasonable proposal, but I think the problem buried in here is quite serious and is being overlooked.</div><div class=""><br class=""></div><div class="">Drew</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 22, 2016, at 3:02 PM, Douglas Gregor via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="" data-mce-href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:</div><div class=""><div style="word-wrap: break-word;" class="" data-mce-style="word-wrap: break-word;"><p style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;">Hello Swift community,</p><p style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;">The review of SE-0005"Better Translation of Objective-C APIs Into Swift" begins now and runs through January 31, 2016. The proposal is available here:</p><blockquote style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px 15px; border-left-width: 4px; border-left-style: solid; border-left-color: #dddddd; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px 15px; border-left-width: 4px; border-left-style: solid; border-left-color: #dddddd; background-color: #ffffff;"><div style="box-sizing: border-box; margin-top: 0px; margin-bottom: 0px;" class="" data-mce-style="box-sizing: border-box; margin-top: 0px; margin-bottom: 0px;"><span color="#777777" face="Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif, Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol" size="3" data-mce-style="color: #777777; font-family: 'Helvetica Neue', Helvetica, 'Segoe UI', Arial, freesans, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol'; font-size: medium;" style="color: #777777; font-family: 'Helvetica Neue', Helvetica, 'Segoe UI', Arial, freesans, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol'; font-size: medium;"><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0005-objective-c-name-translation.md" class="" data-mce-href="https://github.com/apple/swift-evolution/blob/master/proposals/0005-objective-c-name-translation.md">https://github.com/apple/swift-evolution/blob/master/proposals/0005-objective-c-name-translation.md</a></span></div></blockquote><p style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;">Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at</p><blockquote style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px 15px; color: #777777; border-left-width: 4px; border-left-style: solid; border-left-color: #dddddd; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px 15px; color: #777777; border-left-width: 4px; border-left-style: solid; border-left-color: #dddddd; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;"><div style="box-sizing: border-box; margin-top: 0px; margin-bottom: 0px;" class="" data-mce-style="box-sizing: border-box; margin-top: 0px; margin-bottom: 0px;"><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" style="box-sizing: border-box; background-color: transparent; color: #4078c0; text-decoration: none;" class="" data-mce-href="https://lists.swift.org/mailman/listinfo/swift-evolution" data-mce-style="box-sizing: border-box; background-color: transparent; color: #4078c0; text-decoration: none;">https://lists.swift.org/mailman/listinfo/swift-evolution</a></div></blockquote><p style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;">or, if you would like to keep your feedback private, directly to the review manager. When replying, please try to keep the proposal link at the top of the message:</p><blockquote style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px 15px; border-left-width: 4px; border-left-style: solid; border-left-color: #dddddd; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px 15px; border-left-width: 4px; border-left-style: solid; border-left-color: #dddddd; background-color: #ffffff;"><p style="color: #777777; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; box-sizing: border-box; margin-top: 0px; margin-bottom: 16px;" class="" data-mce-style="color: #777777; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; box-sizing: border-box; margin-top: 0px; margin-bottom: 16px;">Proposal link:</p><blockquote style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px 15px; border-left-width: 4px; border-left-style: solid; border-left-color: #dddddd;" class="" data-mce-style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px 15px; border-left-width: 4px; border-left-style: solid; border-left-color: #dddddd;"><div style="box-sizing: border-box; margin-top: 0px; margin-bottom: 0px;" class="" data-mce-style="box-sizing: border-box; margin-top: 0px; margin-bottom: 0px;"><span color="#777777" face="Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif, Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol" size="3" data-mce-style="color: #777777; font-family: 'Helvetica Neue', Helvetica, 'Segoe UI', Arial, freesans, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol'; font-size: medium;" style="color: #777777; font-family: 'Helvetica Neue', Helvetica, 'Segoe UI', Arial, freesans, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol'; font-size: medium;"><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0005-objective-c-name-translation.md" class="" data-mce-href="https://github.com/apple/swift-evolution/blob/master/proposals/0005-objective-c-name-translation.md">https://github.com/apple/swift-evolution/blob/master/proposals/0005-objective-c-name-translation.md</a></span></div></blockquote><p style="color: #777777; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; box-sizing: border-box; margin-top: 0px; margin-bottom: 16px;" class="" data-mce-style="color: #777777; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; box-sizing: border-box; margin-top: 0px; margin-bottom: 16px;">Reply text</p><blockquote style="color: #777777; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; box-sizing: border-box; margin: 0px; padding: 0px 15px; border-left-width: 4px; border-left-style: solid; border-left-color: #dddddd;" class="" data-mce-style="color: #777777; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; box-sizing: border-box; margin: 0px; padding: 0px 15px; border-left-width: 4px; border-left-style: solid; border-left-color: #dddddd;"><div style="box-sizing: border-box; margin-top: 0px; margin-bottom: 0px;" class="" data-mce-style="box-sizing: border-box; margin-top: 0px; margin-bottom: 0px;">Other replies</div></blockquote></blockquote><h5 style="box-sizing: border-box; margin-top: 1em; margin-bottom: 16px; line-height: 1.4; font-size: 1em; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; margin-top: 1em; margin-bottom: 16px; line-height: 1.4; font-size: 1em; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; background-color: #ffffff;"><a id="user-content-what-goes-into-a-review-1" class="anchor" href="https://github.com/apple/swift-evolution#what-goes-into-a-review-1" style="box-sizing: border-box; background-color: transparent; color: #4078c0; text-decoration: none; display: inline-block; padding-right: 2px; margin-left: -18px; line-height: 1.1;" data-mce-href="https://github.com/apple/swift-evolution#what-goes-into-a-review-1" data-mce-style="box-sizing: border-box; background-color: transparent; color: #4078c0; text-decoration: none; display: inline-block; padding-right: 2px; margin-left: -18px; line-height: 1.1;"><span class="octicon octicon-link" style="box-sizing: border-box; font-weight: normal; font-size: 16px; line-height: 1; font-family: 'octicons'; display: inline-block; vertical-align: middle; visibility: hidden;" data-mce-style="box-sizing: border-box; font-weight: normal; font-size: 16px; line-height: 1; font-family: 'octicons'; display: inline-block; vertical-align: middle; visibility: hidden;"></span></a>What goes into a review?</h5><p style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;">The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of Swift. When writing your review, here are some questions you might want to answer in your review:</p><ul style="box-sizing: border-box; padding: 0px 0px 0px 2em; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; padding: 0px 0px 0px 2em; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;"><li style="box-sizing: border-box;" class="" data-mce-style="box-sizing: border-box;">What is your evaluation of the proposal?</li><li style="box-sizing: border-box;" class="" data-mce-style="box-sizing: border-box;">Is the problem being addressed significant enough to warrant a change to Swift?</li><li style="box-sizing: border-box;" class="" data-mce-style="box-sizing: border-box;">Does this proposal fit well with the feel and direction of Swift?</li><li style="box-sizing: border-box;" class="" data-mce-style="box-sizing: border-box;">If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</li><li style="box-sizing: border-box;" class="" data-mce-style="box-sizing: border-box;">How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</li></ul><p style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;">More information about the Swift evolution process is available at</p><blockquote style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px 15px; color: #777777; border-left-width: 4px; border-left-style: solid; border-left-color: #dddddd; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px 15px; color: #777777; border-left-width: 4px; border-left-style: solid; border-left-color: #dddddd; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;"><div style="box-sizing: border-box; margin-top: 0px; margin-bottom: 0px;" class="" data-mce-style="box-sizing: border-box; margin-top: 0px; margin-bottom: 0px;"><a href="https://github.com/apple/swift-evolution/blob/master/process.md" style="box-sizing: border-box; background-color: transparent; color: #4078c0; text-decoration: none;" class="" data-mce-href="https://github.com/apple/swift-evolution/blob/master/process.md" data-mce-style="box-sizing: border-box; background-color: transparent; color: #4078c0; text-decoration: none;">https://github.com/apple/swift-evolution/blob/master/process.md</a></div></blockquote><p style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;">Thank you,</p><p style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;">-Doug Gregor</p><p style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;" class="" data-mce-style="box-sizing: border-box; margin-top: 0px; margin-bottom: 16px; color: #333333; font-family: 'helvetica neue' , 'helvetica' , 'segoe ui' , 'arial' , 'freesans' , sans-serif , 'apple color emoji' , 'segoe ui emoji' , 'segoe ui symbol'; font-size: 16px; background-color: #ffffff;">Review Manager</p></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="" data-mce-href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" data-mce-href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""></div></div></div></div></blockquote></div></body></html>