>> Unless typestandin, typeplaceholder, or adoptedtype are placed on the table, >> I don't really see any reason to introduce a keyword other than >> associatedtype for this proposal. > > +1. associatedtype seems better than any other option I’ve seen thus far > (including the new ones you mentioned).
If the language construct is called an “associated type,” then introducing a keyword that uses any terminology other than “associated” is a recipe for eternal community confusion. I could go for associatedtype, associated_type, or associated — but I agree that anything else, including typealias, seems inferior. P
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
