[swift-evolution] [SE-0011] Re-considering the replacement keyword for "typealias"

Matt Whiteside mwhiteside.dev at gmail.com
Tue Dec 22 23:06:41 CST 2015

I did see that point made earlier in the thread, but I’m not convinced that design for googleability is the right ordering of priorities.  I think people will probably figure out that they need to search for “swift protocol type” or whatever the final choice ends up being.

> On Dec 22, 2015, at 20:54, Brent Royal-Gordon <brent at architechies.com> wrote:
>> I don’t see any problem in referring to the feature as associated types, but then having the syntax be just plain “type”.
> I think it's been said before, but the problem with using a `type` keyword is that if you type "swift type" into Google (or any other search feature you might use for documentation), you're probably not going to get information about this feature specifically. "swift associated" or "swift associatedtype" are more likely to give you what you want.
> -- 
> Brent Royal-Gordon
> Architechies

More information about the swift-evolution mailing list