[swift-evolution] [Review] SE-0023 API Design Guidelines

Joe Groff jgroff at apple.com
Sat Jan 23 12:11:13 CST 2016

> On Jan 23, 2016, at 2:12 AM, Marc Knaup via swift-evolution <swift-evolution at swift.org> wrote:
> What is the rationale behind naming enumeration cases in upper camel case?
> Follow case conventions: names of types, protocols and enum cases areUpperCamelCase. Everything else is lowerCamelCase.
> let a = NSComparisonResult.OrderedSame  // refers to a value, but is upper-case
> let b = NSDate.distantFuture            // refers to a property/value, but is lower-case
> everything related to types (type names, protocol names, generic type parameter names) should be upper camel case
> everything else (function names, property names, variable names, etc.) should be lower camel case
> This is already the current and the proposed recommendation with enumeration cases being the only exception.
> Enumeration cases are not types.

I agree. It would make enum cases feel more consistent with the rest of the language to make them lowerCamelCase.


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

More information about the swift-evolution mailing list