Wouldn't this be covered under SE-0092?<br><div class="gmail_quote"><div dir="ltr">On Mon, Jun 6, 2016 at 15:59 Ross O'Brien via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Given a protocol with an associated type:<div><br></div><div>protocol Foo</div><div>{</div><div> associatedtype Bar</div><div>}</div><div><br></div><div>it should be possible to define a protocol conforming to Foo, for which Bar can be typealiased:</div><div><br></div><div>protocol IntFoo : Foo</div><div>{</div><div> typealias Bar = Int</div><div>}</div><div><br></div><div>such that all conformers to IntFoo now have an associatedtype Bar being Int without having to define it themselves. At present IntFoo cannot declare a typealias (as this generates a warning that typealias has been deprecated), but can declare an 'associatedtype Bar = Int' which types conforming to IntFoo have to repeat to consider it properly declared. This re-declaration is redundant.</div></div>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>