<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Doug,<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Nov 30, 2017, at 4:28 PM, Douglas Gregor 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=""><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">I think this approach is more predictable and more implementable than the current model. I’m curious whether the above makes sense to someone other than me, and whether it covers existing use cases well enough. Thoughts?</div></div></blockquote><br class=""></div><div>I don’t have a lot to add here, except to say: Yes, this makes sense to me, and is much easier to reason about. The three new rough rules covers all of the Swift protocol code I can think of that I’ve written, and seems complete for any reasonable set of thought experiments I’ve come up with so far.</div><br class=""><div class="">Thanks!</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- Greg</div></body></html>