James or Erica (or someone else), can you explain what makes these types "placeholders"? I don't think of the other requirements in a protocol as "placeholder properties" or "placeholder methods".
My explanation of these things is "When a particular type X conforms to a protocol, you can ask about the types that X uses to implement the requirements of the protocol". I guess we could call them "related types" instead of "associated types", but that doesn't seem significantly different. Jordan > On Dec 23, 2015, at 12:42, James Campbell via swift-evolution > <swift-evolution@swift.org> wrote: > > The thing is associated type means nothing to me, it's too technical. > Placeholder type I think would be better even if it's only what we called it > in the documentation > > Sent from my iPhone _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
