<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=""><div><blockquote type="cite" class=""><div class=""><div class="">The `Any<…>` here is acting like a type (actually, it *is* a type, just a slightly special type) and it should be capitalized like a type.</div></div></blockquote><div><br class=""></div><div>One more point around this comment. While `any<MyProtocol>` is a type `any` is <b class="">not</b> a type. `any` is a kind of type. We have classes, structs, enums, and existentials. We don’t capitalize `struct`, `class`, or `enum`. Why should we capitalize `any` just because it is often going to be declared ad-hoc (and again, I think it is worthwhile to give existential types a name in many cases, just as we give other types a name — preferring structs to tuples, for example). Making `any` lowercase emphasizes the fact that it is a <b class="">kind of type</b> rather than a type.</div><div><br class=""></div><div>I really don’t want to come across as argumentative here. I’m just really trying to work out what is best for the language. I will be very happy using a language with generalized existentials regardless of whether we capitalize the `a` or not.</div></div><br class=""><div class="">-Matthew</div></body></html>