<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 Feb 5, 2016, at 11:16 PM, Douglas Gregor 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=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Feb 5, 2016, at 1:32 PM, Dave Abrahams 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=""><div class=""><br class="">Given all the awesome feedback I've gotten on this thread, I went back<br class="">to the drawing board and came up with something new; I think this one<br class="">works. The previously-stated goals still apply:<br class=""></div></div></blockquote><br class=""><blockquote type="cite" class=""><div class=""><div class="">[snip goals]<br class=""></div></div></blockquote><br class=""><blockquote type="cite" class=""><div class=""><div class="">P.S. Doug is presently working on generating new importer results, based<br class=""> on these guidelines, for your perusal. They should be ready soon.<br class=""></div></div></blockquote></div><div class=""><br class=""></div>Here’s a link:<div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/apple/swift-3-api-guidelines-review/pull/10/files" class="">https://github.com/apple/swift-3-api-guidelines-review/pull/10/files</a></div></div></div></blockquote><div><br class=""></div><div>Well, I might be the only one, but I don’t like these diffs. There are only a few cases where I don’t prefer the original function signature. Function names ending in prepositions with no objects look odd to me. It seems like a strange choice to make the split in the middle of the prepositional phrase.</div><div><br class=""></div><div>If, as now proposed, the description of the main focus of the function call is going to be moved from the function name to a label for the first parameter, why not just drop the preposition entirely? As in:</div><div><br class=""></div><div>func copy(zone zone: Zone = nil) -> AnyObject</div><div>func loadValuesAsynchronously(keys keys: [String], completionHandler handler: (() -> Void)? = nil)</div><div>func tracks(mediaType mediaType: String) -> [AVAssetTrack]</div><div><br class=""></div><div>Or put it in the argument label, to keep the prepositional phrase intact:</div><div><br class=""></div><div><div>func copy(withZone zone: Zone = nil) -> AnyObject</div><div>func loadValuesAsynchronously(forKeys keys: [String], completionHandler handler: (() -> Void)? = nil)</div><div>func tracks(withMediaType mediaType: String) -> [AVAssetTrack]</div></div><div><br class=""></div><div>—CK</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="">Feedback welcome!<br class=""><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><div class=""><br class=""></div></div></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>