[swift-evolution] [swift-evolution-announce] [Accepted] SE-0011 Replace `typealias` keyword with `associatedtype` for associated type declarations

Kevin Ballard kevin at sb.org
Sat Jan 9 17:24:20 CST 2016

In the previous thread on this topic, there was a lot of bikeshedding
about the specific keyword. A bunch of people (myself included)
suggested just "associated" instead, some people suggested a few
alternatives (like "type" or "associated type"). I don't recall if
anyone actually explicitly said they prefer the given name
"associatedtype", though there were of course people who voted +1
without opining on the subject at all.

In any case, my point is, given that this proposal is now accepted, are
we committed to the keyword "associatedtype" or is there still room to
pick a different keyword? Enough people in the thread were in favor of
using a different keyword that it seems worth considering.

-Kevin Ballard

On Sat, Jan 9, 2016, at 03:18 PM, Douglas Gregor wrote:
> The review of SE-0011 "Replace `typealias` keyword with
> `associatedtype` for associated type declarations" ran from January
> 3-6, 2016. The proposal has been *accepted*. We will introduce the
> “associatedtype” syntax in Swift 2.2 (deprecating “typealias”) and
> remove the “typealias” syntax in Swift 3.
> https://github.com/apple/swift-evolution/blob/master/proposals/0011-replace-typealias-associated.md
> Thank you to everyone who participated in the review process! We
> welcome an implementation of this proposal, which is tracked by
> https://bugs.swift.org/browse/SR-511
> - Doug
> _________________________________________________
> swift-evolution-announce mailing list swift-evolution-
> announce at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution-announce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160109/49812adb/attachment.html>

More information about the swift-evolution mailing list