[swift-evolution] [Idea] Allowing most keywords after "."

[Sune Foldager]

I’m with Erica on this one. Enum cases to me feel like datatype constructors, and not as members as such (for instance enum Tree { Leaf, Branch }). It makes them stand out more when deconstructing in switch statements. I think it’s unfortunate to switch to lowerCamel.
 
—Sune

> On 27 Feb 2016, at 00:27, Erica Sadun via swift-evolution <swift-evolution at swift.org> wrote:
> 
> I honestly like upper camel. I know my reasons are linguistically unsupported: static members are not types. But it seems to me that a union type, the fully qualified Type.EnumerationCase specifies the memory layout of how the type is realized. 
> 
> Still, I like upper camel. I also like upper case for global functions and constants.
> 
> -- E, out of step, out of sync