I would much prefer one of the longer terms such as 'associatedtype' to 'type'. The simple reason why: I've been using a lot of generics for a while and I still find it tricky. I want a term I can type into a search engine and expect results for, and 'type's too common for that.
On Tue, Dec 22, 2015 at 8:42 PM, Matt Whiteside via swift-evolution < swift-evolution@swift.org> wrote: > The fact that “associated type” is used throughout the documentation is > worth making note of, but it could also be that some other replacement > would make the concept more clear than it currently is in the documentation. > > Matt > > On Dec 22, 2015, at 09:30, Erica Sadun via swift-evolution < > swift-evolution@swift.org> wrote: > > The phrase "associated type" is used throughout the Swift Programming > Language book, for example: "When defining a protocol, it is sometimes > useful to declare one or more *associated types* as part of the > protocol’s definition. An *associated type* gives a placeholder name (or > alias) to a type that is used as part of the protocol. The actual type to > use for that *associated type* is not specified until the protocol is > adopted." > > > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution > >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution