<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="">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.<div class=""><br class=""></div><div class="">Matt</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 22, 2015, at 09:30, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">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 <b class="">associated types</b> as part of the protocol’s definition. An <b class="">associated type</b> gives a placeholder name (or alias) to a type that is used as part of the protocol. The actual type to use for that <b class="">associated type</b> is not specified until the protocol is adopted."</div><div class=""><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>