> for me "associated type" is just a technical term with no obvious meaning.
That's not a bad thing. You get a hint that something funny is going on, and if
you don't know what, you can look it up. You even have a great keyword to
search for, right there.
Compared to that, something like “required type” doesn't tell you much about
the gravity of the change. If you know about required constructors, you could
assume that required types are like that — and they are like that, but they
also change your protocol in a pretty spectacular way.
Anything is better than just “typealias”, though.
A.
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
