<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I’ve had a few discussions about that with Joe and Rob Rix, where I understood less than I’d like to admit :) Joe recently said that the subject of type-erasure is probably not currently planned for Swift 3, but saying that:<div class=""><br class=""></div><div class=""><i class="">@rob_rix @dhartbit Fixing cyclic assoc type references will give us the runtime support for those existentials, at least.</i><div class=""><a href="https://twitter.com/jckarter/status/675322278675001344" class="">https://twitter.com/jckarter/status/675322278675001344</a></div><div class=""><br class=""></div><div class="">If that makes sense to you.</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 14 Dec 2015, at 23:24, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> 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=""><div class=""><div class=""><blockquote type="cite" class=""><div class="">Joe wrote: "What changes would be necessary to the standard library to make the most of this feature? Some particular problems we'd like to solve are to eliminate the need for the AnyGenerator/AnySequence/AnyCollection wrapper types, and to provide a solution for heterogeneous equality, so that protocols can inherit Equatable and Hashable without forfeiting the ability to be used dynamically. See Brent Simmons' Swift diary posts at <a href="http://inessential.com/swiftdiary" class="">http://inessential.com/swiftdiary</a> for an example of why the latter is important."</div></blockquote></div><div class=""><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class=""><br class=""></div><div class="">Any advice for what could be done now in preparation for any changes that might happen and an estimate of when these types might be on the chopping block? Not 3.0, right? But 4.0? What are good ways to work around this now using current (and presumably stable) constructs?</div><div class=""><br class=""></div><div class="">Thanks, -- E</div><div class=""><br class=""></div></div></div></div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=nE9rxSXA5G4kxsTVkgv43hXwizS3O2z60WweqomIrdgMgwGEOrAzuc7QO0EZPs0SyypiWs198HfIRa7kk2RsRGWCjT5rZBlvNCfm2Ie1jdPti2XlaNB0zMqk1sgXge-2Ffqt1Cg6yS4meeakRZKJuBDgSW-2FATPYcYhNH5EkGblazqQBiTgft15NPqJiCDngUn8MazqmRTxv5Q6XPo20yzRwVd-2BCSe9rZCPbsnriTuMgm4-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
</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></div></body></html>