<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="">Le 11 nov. 2017 à 16:48, Joe Groff via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: SFUIDisplay-Regular; font-size: 15px; 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; float: none; display: inline !important;" class="">That'd be great, but Swift violates Gilad Bracha's golden rule by having static overloading, and throws bidirectional type inference on top, so our static name resolution can't be treated as a specialization of a dynamic name lookup mechanism in all cases.</span><br style="font-family: SFUIDisplay-Regular; font-size: 15px; 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;" class=""></div></blockquote></div><br class=""><div class="">I didn't know of Gilad Bracha, so you made me curious. </div><div class=""><br class=""></div><div class="">I guess that the "golden rule" you refer to is here, for anyone curious: <a href="https://gbracha.blogspot.fr/2009/09/systemic-overload.html" class="">https://gbracha.blogspot.fr/2009/09/systemic-overload.html</a></div><div class=""><br class=""></div><div class="">Gwendal Roué</div><div class=""><br class=""></div></body></html>