<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 Mar 15, 2016, at 10:41 AM, Jordan Rose 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=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Thank you! I realized one other potential flaw in the data-gathering: your search for "func foo(_ bar" will match both Objective-C methods and C functions. I'm not sure CF should really be contributing to the scores. Unfortunately the main way I can think of to differentiate them is by indentation, which seems a little sketchy.</div><div class=""><br class=""></div><div class="">Still, the conclusions I would draw from this are that the <i class="">vast</i> majority of methods fall into one of the three following categories:</div><div class=""><br class=""></div><div class="">- No arguments.</div></div></div></blockquote><div><br class=""></div>No harm, no foul situation.</div><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="">- Empty first argument label.</div></div></div></blockquote><div><br class=""></div><div>Change would primarily affect adding "_ ", two characters</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="">- First argument label that does not match the parameter name.</div></div></div></blockquote><div><br class=""></div><div>No harm, no foul situation.</div><div><br class=""></div><div>I still feel that adding consistency outweighs the inconvenience of the two extra characters, </div><div>which then show an *intent* that the argument label is empty by choice rather than convention.</div><div><br class=""></div><div>-- E</div><div><br class=""></div><blockquote type="cite" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">This doesn't mean we shouldn't change the convention—"_ completionHandler" is much easier to type than "completionHandler completionHandler", and it's still removing complexity—but it does mean (to me) that the new API naming guidelines <i class="">don't</i> make the "matching" case more important; they only make the "no label" case <i class="">less</i> important.</div><div class=""><br class=""></div><div class="">Jordan</div></div></blockquote></div><br class=""></body></html>