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

Andrey Tarantsov andrey at tarantsov.com
Sun Dec 20 05:21:13 CST 2015

Aren't we bikeshedding here? These are all good names; I think we can pick one, and leave the final choice to the core team.

My personal preference is for something like “associated type X” or “associated typealias X” — no need for an underscore when you can require a space. Right now “typealias” is probably the word to use, although if Swift later introduces “type”, that would be a better choice. And I see “associated” as a context-specific modifier anyway; could even be spelled “@associated” (I'm still unclear about the rules about @/no-@).


More information about the swift-evolution mailing list