<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 21, 2015, at 9:04 PM, Charles Kissinger 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=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 21, 2015, at 3:58 PM, Michael Wells 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="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I love that Swift has a published API design guidelines at <a href="https://swift.org/documentation/api-design-guidelines.html" class="">https://swift.org/documentation/api-design-guidelines.html</a>, but one thing about it bugs me: the use of <b class="">UpperCamelCase</b> for cases. I know this ship has long sailed, but why didn't the team choose <b class="">lowerCamelCase</b> for these? The current style seems inconsistent and requires an “instances are lowerCamelCase, aside from Enums” clarification.</div><div class=""><br class=""></div><div class="">-mw<br class=""><div class=""><div class=""><br class=""></div></div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=F5lQLlMRbBDxNsThVg1FdUgz-2B2V4-2F7uZCaKOBKqUINL8N7mgEDFkpmDFfsmEvveGwdmNZf3sWkuh-2BLOJ7I3-2BqolgJyb26mw-2Fx6SmzXgkk8lTzrcU-2BemovawRNF68GBiL5YPSt90vBbTfQQ7NuvDDdPiWKf0vO1gLSpEsK9P0srMvD6y8kAfN0FDix8I9jTqBs6fnPpasqy3JXu1FDx1hNg-3D-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="">
</div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote><br class=""></div><div class="">Some differences of opinion here might arise from the fact that simple enums act as constants, but enums with associated values seem (to me anyway) to function much more like subtypes with RTTI built in. lowerCamelCase makes sense for the former, but UpperCamelCase for the latter.</div></div></div></blockquote><br class=""></div><div>For non-enum constants, we use lowerCamelCase, for example Int.max, or UIColor.redColor.</div><div><br class=""></div><div>-Joe</div><br class=""></body></html>