<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 also really like the proposal but prefer the ‘associated’ keyword instead of ‘associatedtype’. Here is my review:</div><div class=""><br class=""></div><div class=""><b class="">What is your evaluation of the proposal?</b><br class=""><br class="">Big +1 from me. I remember that the typealias keyword in protocols confused me for quite a while: the concept of associated types is already complicated to grasp coming from a different generics model, but overloading the typealias keyword doesn’t help in the learning process. Like I said above, I would vote for the ‘associated’ keyword. Even if grammatically more correct, ‘associatedtype’ seems like a mouthful for me.<br class=""><br class=""><b class="">Is the problem being addressed significant enough to warrant a change to Swift?</b><br class=""><br class="">I strongly think so.<br class=""><br class=""><b class="">Does this proposal fit well with the feel and direction of Swift?</b><br class=""><br class="">Yes.<br class=""><br class=""><b class="">If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</b><br class=""><br class="">After learning about associated types, I researched Scala traits and it helped me understand the concept better and enjoyed that Scala uses a clearly defined keyword.<br class=""><br class=""><b class="">How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</b><br class=""><br class="">I followed the original discussion but haven’t found time to read all reviews before mine.</div><br class=""><div><blockquote type="cite" class=""><div class="">On 08 Jan 2016, at 01:13, Alex Popov 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="compose" style="padding-left: 20px; padding-right: 20px; padding-bottom: 8px;" class="" applecontenteditable="true"><div class="">Data of 1: I am disappointed by the choice, but remain silent so I don't look like a nit picker <i class="">and</i> to not further clutter the mailing list. </div><div class=""><br class=""></div><div class="">I find `associatedtype` to be clearer, but `associated` to be much more pleasant to read and write. </div><div class=""><br class=""></div><div class=""> * What is your evaluation of the proposal?</div><div class=""><br class=""></div><div class="">+1 for the proposal, I didn't know associated types in protocols where even a thing, I just thought it was black-typealias-magic that was out of my intellectual reach. </div><div class=""><br class=""></div><div class=""> * Is the problem being addressed significant enough to warrant a change to Swift?</div><div class=""><br class=""></div><div class="">Definitely.</div><div class=""><br class=""></div><div class=""> * Does this proposal fit well with the feel and direction of Swift?</div><div class=""><br class=""></div><div class="">I do believe this proposal fits well with Swift, regardless of keyword chosen.</div><div class=""><br class=""></div><div class=""> * If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</div><div class=""><br class=""></div><div class="">Not applicable</div><div class=""><br class=""></div><div class=""> * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</div><div class=""><br class=""></div><div class="">I have been following the proposal from the start, and have read up on Associated Types in protocols. <br class=""><br class=""><div class="acompli_signature">Alex Popov Jr.<br class="">Principal iOS developer | Shelfie<br class=""><a dir="ltr" href="http://www.shelfie.com/" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="1" class="">www.shelfie.com</a> | @getshelfie</div><br class=""></div></div>
<div class="gmail_quote">_____________________________<br class="">From: Tino Heth via swift-evolution <<a dir="ltr" href="mailto:swift-evolution@swift.org" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="2" class="">swift-evolution@swift.org</a>><br class="">Sent: Thursday, January 7, 2016 15:22<br class="">Subject: Re: [swift-evolution] [Review] Replace `typealias` keyword with `associatedtype` for associated type declarations<br class="">To: Erica Sadun <<a dir="ltr" href="mailto:erica@ericasadun.com" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="5" class="">erica@ericasadun.com</a>><br class="">Cc: Swift Evolution <<a dir="ltr" href="mailto:swift-evolution@swift.org" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="6" class="">swift-evolution@swift.org</a>><br class=""><br class=""><br class="">Hi Erica,<br class=""><br class="">sorry for the late reaction — but I've been busy writing code instead of emails ;-)<br class=""><br class="">> Why secrecy? There is none. I was asked to run a poll. I ran a poll using the best information I had at the moment.<br class=""><br class="">I hope I could clear up some misunderstandings in the answer to Chris (no conspiracy theory here ;-) and that you don't have the impression I'm accusing you for the poll (I consider it to be an act of pure kindness).<br class="">Maybe you even agree with me partially about the potential dangers of surveys:<br class="">I still wonder why no one complained that "associated" wasn't chosen, despite being the most popular option. Sure, some may have changed their mind, but even now, there are people saying they prefer that discarded possibility.<br class="">I can think of four possible explanations for this observation (all of them with a share of "the actual keyword is so unimportant, I don't really care"):<br class="">- all changed their mind (great — everyone is happy)<br class="">- participants lost their interest and have never seen the final proposal<br class="">- participants are disappointed by the choice, but remain silent because they don't want to look like nitpickers<br class="">- participants are disappointed by the choice, but remain silent because they lost faith in the process<br class=""><br class="">I guess the last one is to dramatic to be real (I've been referring to the community process; I never had much faith in polls ;-), but the first is the only one that leaves no sour taste...<br class=""><br class="">Best regards,<br class="">Tino<br class=""><br class="">To quash possible rumors: I personally do my nitpicking loud and proud, and I didn't start this tiny meta-discussion in frustration — as long as I only have to use the word with working autocompletion, "associatedtype" is fine for me ;-)<br class="">_______________________________________________<br class="">swift-evolution mailing list<br class=""><a dir="ltr" href="mailto:swift-evolution@swift.org" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="8" class="">swift-evolution@swift.org</a><br class=""><a dir="ltr" href="https://lists.swift.org/mailman/listinfo/swift-evolution" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="9" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""><br class=""><br class=""></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=nE9rxSXA5G4kxsTVkgv43hXwizS3O2z60WweqomIrdiu-2FRN0hpm3AMd0r3HHMiLnOKcLlZealcEnpS6055DyaiwvDwniskRxhBLZ6IFaFWImNEaqWnbk7CAJHO-2B3BQVoiGfY4qoNjv2fRzQzcO84LpeWBpjt-2F9kdIR0lvQ3i-2B40-2Ff2aHmnwzg1g0FDwum3GLTwggRchK6Luay1Rd8oFES8C023Bgn8Lisk6I2qKjo-2B8-3D" alt="" width="1" height="1" border="0" style="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;" class="">
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>