<div dir="ltr"><div><span style="white-space:pre-wrap">></span> What is your evaluation of the proposal?</div><div><br></div><div>+1 for changing the name, but -1 for "associatedtype" in particular. Alternate suggestions:</div><div><br> - associatedType Element<br></div> - associated_type Element<div> - associated type Element<br><div><div> - associated Element</div><div> - type Element</div><div> - having Element</div><div><br></div><div><br></div><div><span style="white-space:pre-wrap">></span> Is the problem being addressed significant enough to warrant a change to Swift?</div><div><br></div><div>Yes.</div><div><br></div><div><br></div><div><span style="white-space:pre-wrap">></span> Does this proposal fit well with the feel and direction of Swift?</div><div><br></div><div>I don't feel that the multi-word-yet-all-lowercase name fits with the rest of the Swift language. See alternate suggestions above.</div><div><br></div><div><br></div><div><span style="white-space:pre-wrap">></span> How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</div></div></div><div><br></div><div>Extensive experience with the feature, but I have mostly just skimmed the emails in this (and the preceding) thread.</div><div><br></div><div class="gmail_extra"><div><div><div dir="ltr"><div>- Jacob<br></div></div></div></div>
<br><div class="gmail_quote">On Sat, Jan 2, 2016 at 10:38 PM, Douglas Gregor via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hello Swift community,<div><br></div><div>The review of "Replace `typealias` keyword with `associatedtype` for associated type declarations” begins now and runs through Wednesday, January 6th. The proposal is available here:</div><div><br></div><div><span style="white-space:pre-wrap"> </span><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0011-replace-typealias-associated.md" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0011-replace-typealias-associated.md</a></div><div><br></div><div><div>Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at</div><div><br></div><div><span style="white-space:pre-wrap"> </span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a></div><div><br></div><div>or, if you would like to keep your feedback private, directly to the review manager.</div><div><br></div><div>What goes into a review?</div><div><br>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:<br><br><div><span style="white-space:pre-wrap"> </span>* What is your evaluation of the proposal?<br></div><div><span style="white-space:pre-wrap"> </span>* Is the problem being addressed significant enough to warrant a change to Swift?<br></div><div><span style="white-space:pre-wrap"> </span>* Does this proposal fit well with the feel and direction of Swift?<br></div><div><span style="white-space:pre-wrap"> </span>* If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br></div><div><span style="white-space:pre-wrap"> </span>* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br></div><br></div><div>More information about the Swift evolution process is available at</div><div><br></div><div><span style="white-space:pre-wrap"> </span><a href="https://github.com/apple/swift-evolution/blob/master/process.md" target="_blank">https://github.com/apple/swift-evolution/blob/master/process.md</a></div><div><br></div><div><span style="white-space:pre-wrap"> </span>Cheers,</div><div><span style="white-space:pre-wrap"> </span>Doug Gregor</div><div><span style="white-space:pre-wrap"> </span>Review Manager</div></div><div><br></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=P-2BsYbBZHRBuLDBJaL4DIKDNfkkjpROowTyRAObV11qwZB1PyMSa8JgJekaBtrS5hZMeStW-2FVfY9StGKaeo3lkvu7Jkp2jQGofOm4FeVCSj0bz4Ya6yClsPX0B-2FyvNklq6hHMwQaGVfukwJ-2BhsBFveMs0zPJk0PFCDBiQdrS6MTsNC6Hvkj-2FsH2x-2Fgi15wlLd2IIzkByyJJmYyPoYewRoiqIvutaAYyq4JWYNVlNpmc0-3D" alt="" width="1" height="1" border="0" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important">
</div>
<br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div></div>