<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 Jul 1, 2016, at 2:02 PM, Rick Mann via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Alegreya-Regular; font-size: 15px; 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; float: none; display: inline !important;" class="">The problem is, you can never be sure what was intended in the method two(), below:</span></div></blockquote></div><br class=""><div class="">Sure you can. It’s easy to tell that it calls the instance method, because if it were calling the class method there would have to be a “Foo.” in front of it.</div><div class=""><br class=""></div><div class="">You’re first arguing that class-method calls should have the same syntax as instance-method calls, and then complaining that having class and instance methods with the same name is ambiguous … but the reason for the ambiguity is because they’d be hard to tell apart using your proposed syntax. That’s not coherent.</div><div class=""><br class=""></div><div class="">—Jens</div></body></html>