<div dir="ltr">It seems no different to me than when "instancetype" was added to Objective C (though, that doesn't say anything for the 'Swiftiness' of it).<div><br></div><div>Ross</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 6, 2016 at 9:08 PM, Jacob Bandes-Storch 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 dir="ltr">I'm sure we're just bikeshedding at this point, but...<div><br></div><div>I find "typealias" and "fallthrough" much easier to read, and easier to write, than "associatedtype". Upon further in(tro)spection, I think I'm reading typealias and fallthrough as <a href="https://en.wikipedia.org/wiki/English_compound" target="_blank">compound words</a>, rather than multiple words with no separation, so there is no question that they should be all-lowercase.<div><br></div><div>I find associatedtype harder to interpret as a compound word, so I'd expect some separation, either associated_type or associatedType. (I put some other suggestions that I like better in my previous email, though.)</div><div class="gmail_extra"><br clear="all"><div><div><div dir="ltr"><div>Jacob<br></div></div></div></div><div><div class="h5">
<br><div class="gmail_quote">On Wed, Jan 6, 2016 at 12:56 PM, Loïc Lecrenier <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"><span>><br>
> What about the all lower case “associatedtype”? The underscore alternative of “associated_type” breaks existing language precedent. The camel case version (“associatedType”) does have language precedent, and I wonder if it wouldn’t be a better choice:<br>
><br>
> dynamicType<br>
> didSet<br>
> willSet<br>
><br>
> However, there’s also precedent for making paired words all lowercase in keywords:<br>
><br>
> typealias<br>
> fallthrough<br>
> deinit ←(debatable: could be considered single word or hyphenated)<br>
><br>
> Perhaps keyword capitalization conventions deserve some attention across the board.<br>
<br>
</span>I thought the rules were:<br>
- property/method: lowerCamelCase<br>
- language keyword: lowercase<br>
<br>
I consider<br>
- dynamicType as a property<br>
- didSet, willSet, deinit as methods.<br>
- typealias, fallthrough as language keywords<br>
<br>
And “associatedtype” would be a language keyword too, so it is lowercase 😊<br>
<br>
Loïc<br>
<div><div>_______________________________________________<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>
</div></div></blockquote></div><br></div></div></div></div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=-2F-2BoYEebT9nJ6Tn1eM4dmwhL8-2BwH5ixcf4jim0iIuN5xQ291stCQ2UGxNqeIE5ayEYpZvDh1c23-2FpLPECAADm1hSh4QEZhg-2FJCn3hvAz0iO-2BRRD1DEvd3oq4xieZvCh9koc3fnHTDuV09-2FBL6bWi3l7ANdhhYrrslD7LbR0lRWQ3GWHvD924U1R3Ujw3bGlYy58Nts7Gt1Lgf4qoqs-2BusayiSviBkSyoQ1NlF-2FmYDdBQ-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">
<br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">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>