<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="">+1. It's not whether the "of" is on its own or not, it's whether it's describing the base noun or extracting something from it.</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">NSFont.userFont(ofSize: bestSizeForThursdays)</div><div class="">tiffFile.removeImageRepresentation(ofSize: CGSize(width: 16, height: 16)) // hypothetical, importer default would be "of:" but that looks wrong</div></blockquote><div class=""><br class=""></div><div class="">vs.</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">items.appendContentsOf(newItems)</div><div class="">tabView.frameOf(subview: contentView) // hypothetical, could go either way?</div></blockquote><div class=""><br class=""></div>Jordan<br class=""><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 11, 2016, at 11:57, Xiaodi Wu 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="">Huge improvement overall moving the 'of'. However, these and related<br class="">functions stand out as regressing in clarity:<br class="">'''<br class="">- class func userFont(ofSize fontSize: CGFloat) -> NSFont?<br class="">- class func userFixedPitchFont(ofSize fontSize: CGFloat) -> NSFont?<br class="">+ class func userFontOf(size fontSize: CGFloat) -> NSFont?<br class="">+ class func userFixedPitchFontOf(size fontSize: CGFloat) -> NSFont?<br class="">'''<br class="">My rationalization: here, 'of' is being used differently than in other<br class="">places. In fact, userFont(ofSize:) could be equally renamed<br class="">userFont(withSize:) or userFont(havingSize:).<br class=""><br class=""><br class="">On Thu, Feb 11, 2016 at 1:35 PM, Douglas Gregor via swift-evolution<br class=""><<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><blockquote type="cite" class=""><br class=""><blockquote type="cite" class="">On Feb 11, 2016, at 10:53 AM, Dave Abrahams via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class=""><br class="">on Thu Feb 11 2016, Charles Kissinger <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class=""><blockquote type="cite" class="">FWIW, I think these new guidelines strike a very nice balance between<br class="">all of the competing concerns. The result of applying them to some of<br class="">my own code could best be described as “different but not unpleasant”<br class="">;-)<br class=""><br class="">In looking over the diffs, one nice result I didn’t expect is that<br class="">moving the prepositional phrases into the first argument label seems<br class="">to increase the speed with which I absorb the general intent of a<br class="">function -- the “at a glance” understanding -- by moving a “detail”<br class="">(important as it might be) into the parameter list. (The split<br class="">prepositional phrases had the opposite effect for me.)<br class=""></blockquote><br class="">That's nice! What do you think about moving “of” back out of the<br class="">parens? Does that help or hurt?<br class=""></blockquote><br class=""><br class="">And lo!, a diff appeared!<br class=""><br class=""> <a href="https://github.com/apple/swift-3-api-guidelines-review/commit/3f965346f1edea804a9bc6223d2824f43687e92f" class="">https://github.com/apple/swift-3-api-guidelines-review/commit/3f965346f1edea804a9bc6223d2824f43687e92f</a><br class=""><br class=""> - Doug<br class=""><br class="">_______________________________________________<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=""></blockquote>_______________________________________________<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></div></blockquote></div><br class=""></body></html>