<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="">On Dec 21, 2015, at 5:58 PM, Michael Wells via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><div><blockquote type="cite" class=""><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></div></blockquote></div><br class=""><div class="">I’d support this in principle.</div><div class=""><br class=""></div><div class="">The current uppercase convention is widespread enough that I’d really want some sort of alias-and-deprecate mechanism if the guideline were to change.</div><div class=""><br class=""></div><div class="">Cheers, P</div><div class=""><br class=""></div></body></html>