[swift-evolution] Swift case conventions for Enums

Joe Groff jgroff at apple.com
Tue Dec 22 09:27:06 CST 2015

> On Dec 21, 2015, at 9:04 PM, Charles Kissinger via swift-evolution <swift-evolution at swift.org> wrote:
>> On Dec 21, 2015, at 3:58 PM, Michael Wells via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> I love that Swift has a published API design guidelines at https://swift.org/documentation/api-design-guidelines.html <https://swift.org/documentation/api-design-guidelines.html>, but one thing about it bugs me: the use of UpperCamelCase for cases. I know this ship has long sailed, but why didn't the team choose lowerCamelCase for these? The current style seems inconsistent and requires an “instances are lowerCamelCase, aside from Enums” clarification.
>> -mw
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
> 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.

For non-enum constants, we use lowerCamelCase, for example Int.max, or UIColor.redColor.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151222/462c30a2/attachment.html>

More information about the swift-evolution mailing list