<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=""><div class=""><div class="">+1</div><div class=""><br class=""></div><div class="">I'd like the same rules for subscripts:</div><div class=""><br class=""></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class="">e.g. public subscript (<b class="">_ index</b>: Int) -> Element</div></div></blockquote><div class=""><div class=""><br class=""></div><div class="">And also for closures, so that the Clang Importer can use the same block parameter names as Objective-C:</div><div class=""><br class=""></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class="">e.g. public func enumerateByteRanges(_ block: (<b class="">_ bytes</b>: UnsafePointer<Void>, <b class="">_ byteRange</b>: NSRange, <b class="">_ stop</b>: UnsafeMutablePointer<ObjCBool>) -> Void)</div></div></blockquote><div class=""><div class=""><br class=""></div><div class="">The latter wouldn't affect public API, but could be used in Xcode's auto-completion of the trailing closure.</div><div class=""><br class=""></div><div class="">-- Ben</div></div><br class=""><div><blockquote type="cite" class=""><div class="">On 9 Mar 2016, at 18:58, Joe Groff 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="">Our accepted naming guidelines have embraced first argument labels for functions and methods. This weakens our justification for making the first parameter declaration in a `func` declaration behave differently from the others, implicitly being unlabeled. It seems pretty clear to me we should make all of the parameter declarations behave uniformly:<div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">func foo(x: Int, y: Int) // Should declare foo(x:y:), instead of foo(_:y:)</div><div class="">func foo(_ x: Int, y: Int) // Explicitly declares foo(_:y:)</div><div class=""><br class=""></div></blockquote>This would also make `init` and `func` parameters behave consistently, which is nice. There may still be hope for our keyword argument rules to one day be shorter than the Smalltalk spec…<br class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><br class=""></div></blockquote>-Joe</div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>