<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I'm not quite what would be the behavior of this in the proposal:<div class=""><br class=""></div><div class="">extension&nbsp;IntBag&nbsp;: StringBag {<div class="">&nbsp; &nbsp; associatedtype Element = Element</div><div class="">}</div></div><div class=""><br class=""></div><div class="">since both IntBag and StringBag are classes - would IntBag use StringBag's code, but replace String with Int? Or would it just contain both&nbsp;</div><div class=""><br class=""></div><div class="">func&nbsp;object(at&nbsp;index:&nbsp;Int)&nbsp;-&gt;&nbsp;Int?</div><div class=""><br class=""></div><div class="">and</div><div class=""><br class=""></div><div class="">func&nbsp;object(at&nbsp;index:&nbsp;Int)&nbsp;-&gt;&nbsp;String?</div><div class=""><br class=""></div><div class="">if that is the case, what if the protocol contains a non-generic function like</div><div class=""><br class=""></div><div class="">func countElements() -&gt; Int</div><div class=""><br class=""></div><div class="">?</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 25, 2016, at 8:35 PM, Austin Zheng via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi all,<div class=""><br class=""></div><div class="">Thank you for all your comments and feedback! I've rewritten and expanded the proposal to address as many peoples' concerns as possible.</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Austin</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jun 24, 2016, at 10:50 PM, Austin Zheng &lt;<a href="mailto:austinzheng@gmail.com" class="">austinzheng@gmail.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hello all,<div class=""><br class=""></div><div class="">Per Chris Lattner's list of open Swift 3 design topics (<a href="http://article.gmane.org/gmane.comp.lang.swift.evolution/21369" class="">http://article.gmane.org/gmane.comp.lang.swift.evolution/21369</a>), I've put together a proposal for removing type inference for associated types.</div><div class=""><br class=""></div><div class="">It can be found here:&nbsp;<a href="https://github.com/austinzheng/swift-evolution/blob/az-assoctypeinf/proposals/XXXX-remove-assoctype-inference.md" class="">https://github.com/austinzheng/swift-evolution/blob/az-assoctypeinf/proposals/XXXX-remove-assoctype-inference.md</a></div><div class=""><br class=""></div><div class="">Thoughts, criticism, and feedback welcome. There are at least two slightly different designs in the proposal, and I'm sure people will have ideas for even more.</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Austin</div></div></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></div></body></html>