<div dir="ltr">While enum cases may not be types from a compiler perspective, I think they are from a user's level.<div><br></div><div>Consider:<br><br></div><div><div>enum MyError: ErrorType {</div><div> case FileError(fileName: String)</div><div> case SocketError(ipAddr: String, port: Int16)</div><div>}</div></div><div><br></div><div>From a compiler perspective, it's a tagged union (one type), but for a user this is a set of disjoint types that happen to share the same space and have exhaustiveness checking, etc. It's a much more efficient and convenient version of multiple structs or tuples.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 23, 2016 at 1:49 PM, Joe Groff <span dir="ltr"><<a href="mailto:jgroff@apple.com" target="_blank">jgroff@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On Jan 23, 2016, at 10:24 AM, Trent Nadeau <<a href="mailto:tanadeau@gmail.com">tanadeau@gmail.com</a>> wrote:<br>
><br>
> I think it makes sense for enum cases to be UpperCamelCase as they can be thought of as scoped types (singleton types in the case of cases with no associated types).<br>
<br>
</span>They aren't, though. I don't see much value in setting false expectations.<br>
<span class="HOEnZb"><font color="#888888"><br>
-Joe<br>
<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Trent Nadeau</div>
</div>