<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 3, 2016, at 10:40 AM, Andrey Tarantsov <<a href="mailto:andrey@tarantsov.com" class="">andrey@tarantsov.com</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=""><blockquote type="cite" class=""><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class="">Protocol requirements with default (no-op) implementations already satisfy that design goal, no?</div></div></div></blockquote><br class=""></div><div class="">Chris, as we've discussed in a thread that I think got forked from this one:</div><div class=""><br class=""></div><div class="">Yes, they do technically, but it would be nice to both:</div><div class=""><br class=""></div><div class="">1) make it an obvious documented part of the signature, possibly including the default return value</div><div class=""><br class=""></div><div class="">2) possibly make it less verbose by getting rid of the explicitly spelled out protocol extension</div></div></div></blockquote><br class=""></div><div>Right, but “more is worse” when it comes to language design. Having a "more general" facility that greatly overlaps with a “more narrow” facility always makes us question whether it is worth the complexity to have both.</div><div><br class=""></div><div>-Chris</div><br class=""></body></html>