<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 Jan 11, 2016, at 11:38 AM, Tino Heth <<a href="mailto:2th@gmx.de" class="">2th@gmx.de</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="">I haven't had issues with ambiguous function names, but it just feels odd that there is no elegant way to solve those problems, so I agree that something should be done here.<div class=""><br class=""></div><div class="">Speaking of the details, "(" always is an indication to me that there is a function to be called (not only referenced). Are there any special reasons for the parenthesis in this context?</div></div></div></blockquote><div><br class=""></div><div>That’s how we write Swift function names: basename(arglabel1:arglabel2:…arglabelN:).</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Wouldn't parsing be easier when we just leave out "(", ")" and "_”?</div></div></div></blockquote><div><br class=""></div><div>Parsing is easy either way.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><pre class="" style="color: rgb(51, 51, 51); box-sizing: border-box; overflow: auto; font-family: Consolas, 'Liberation Mono', Menlo, Courier, monospace; font-size: 14px; margin-top: 0px; margin-bottom: 0px; line-height: 1.45; padding: 16px; background-color: rgb(247, 247, 247); border-top-left-radius: 3px; border-top-right-radius: 3px; border-bottom-right-radius: 3px; border-bottom-left-radius: 3px; word-wrap: normal; word-break: normal;"><span class="pl-k" style="box-sizing: border-box; color: rgb(167, 29, 93);">let</span> fn1 <span class="pl-k" style="box-sizing: border-box; color: rgb(167, 29, 93);">=</span> someView<span class="pl-k" style="box-sizing: border-box; color: rgb(167, 29, 93);">.</span>insertSubview:aboveSubview:</pre><div class="">imho looks better.</div></div></div></div></blockquote><br class=""></div><div>Sometimes the first argument has a label, so just dropping it doesn’t actually work. It would have to be</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>let fn1 = someView.insertSubview:_:aboveSubview:</div><div><br class=""></div><div>or </div><div><br class=""></div><div><div><span class="Apple-tab-span" style="white-space: pre;"> </span>let fn1 = someView.insertSubview::aboveSubview:</div><div class=""><br class=""></div></div><div>which looks almost like the Objective-C selector, but isn’t. And it doesn’t match the way these methods are called.</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><div><br class=""></div><br class=""></body></html>