<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br>Sent from my iPad</div><div><br>On Apr 28, 2016, at 6:20 PM, Erica Sadun <<a href="mailto:erica@ericasadun.com">erica@ericasadun.com</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><br class=""><div><blockquote type="cite" class=""><div class="">On Friday, 29 April 2016, Matthew Johnson via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><div class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto" class=""><div class="">Does that mean the conformance declaration will be accepted by the compiler under your proposal? I would really like to see this called out explicitly in the proposal.</div></div></blockquote></div></blockquote><br class=""></div><div>I'm making live updates at the gist in response to on-list discussions:</div><div><br class=""></div><div><a href="https://gist.github.com/erica/fc66e6f6335750d737e5512797e8284a" class="">https://gist.github.com/erica/fc66e6f6335750d737e5512797e8284a</a></div><div><br class=""></div><div>If you have specific suggestions for modifications, I'll be happy to evaluate for incorporation.</div></div></blockquote><div><br></div><div>Unfortunately I don't have specific suggestions as there are flaws with all of the approaches I can think of. However, I do think *something* needs to be specified regarding behavior when retroactively conforming a type from a different module which doesn't know anything about the protocol but does implement the requirements (as normal methods). I can't determine how I feel about this proposal without seeing it clearly specified.</div><div><br></div><div><br></div><br><blockquote type="cite"><div><div><br class=""></div><div>-- E</div><div><br class=""></div></div></blockquote></body></html>