<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 10, 2016 at 9:05 PM, Matthew Judge <span dir="ltr"><<a href="mailto:matthew.judge@gmail.com" target="_blank">matthew.judge@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><span><br>
<br>
> On Feb 10, 2016, at 18:17, Dave Abrahams <<a href="mailto:dabrahams@apple.com">dabrahams@apple.com</a>> wrote:<br>
><br>
><br>
>> on Wed Feb 10 2016, Matthew Judge <<a href="http://matthew.judge-AT-gmail.com" target="_blank" rel="noreferrer">matthew.judge-AT-gmail.com</a>> wrote:<br>
>><br>
>> On Tue, Feb 9, 2016 at 2:18 PM, Dave Abrahams via swift-evolution <<br>
>> <a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
>><br>
>>><br>
>>> Hi everybody,<br>
>>><br>
>>> Having looked at some examples, the API guidelines working group members<br>
>>> that were present this morning agreed we really want prepositions inside<br>
>>> the parentheses of method calls.<br>
>>><br>
>>> Here are some results for the importer; we're still tuning some of the<br>
>>> heuristics but overall we feel very good about the preposition<br>
>>> placement:<br>
>>><br>
>>><br>
>>> <a href="https://github.com/apple/swift-3-api-guidelines-review/commit/da7e512cf75688e6da148dd2a8b27ae9efcb8821?diff=split" target="_blank" rel="noreferrer">https://github.com/apple/swift-3-api-guidelines-review/commit/da7e512cf75688e6da148dd2a8b27ae9efcb8821?diff=split</a><br>
>>><br>
>>> Note that this is not final wording, but here are the guidelines we're<br>
>>> working with for first argument labels:<br>
>>><br>
>>> A. Try to form a grammatical phrase including the first argument and<br>
>>> describing the primary semantics at the call site.<br>
>><br>
>> I assume that A is intended to cover:<br>
>><br>
>> a.addObserver(b) // yes<br>
>> a.add(observer: b) // no<br>
><br>
> I don't know what you mean by "cover." It isn't intended to assign the<br>
> "yes/no" decision to those; they both form (the same) grammatical phrase<br>
> at the call site. The choice between those two is governed by B, below.<br>
<br>
</span>By cover I meant assign the "yes/no" decision. So because the first argument is part of the primary semantics, it doesn't get an argument label (per B.1) and the word observer needs to be in the base name so as not to change the semantic meaning.<br>
<div><div class="h5"><br>
><br>
>> I believe I can read this behavior into A by inferring "a grammatical<br>
>> phrase including [the base name and] the first argument" but I want to make<br>
>> sure this is the intent.<br>
>><br>
>>><br>
>>> B. The first argument gets a label when and only when:<br>
>>><br>
>>> 1. It does not form part of a grammatical phrase describing the<br>
>>> primary semantics. For example,<br>
>>> ```<br>
>>> x.dismiss(animated: y)<br>
>>> ```<br>
>>> [more examples needed]<br>
>>> Note that parameters with defaults never describe the primary<br>
>>> semantics. so are always labeled.<br>
>>> ```<br>
>>> func invert(options options: SomeOptionSet = []) // yes<br>
>>> func invert(_ options: SomeOptionSet = []) // no<br>
>>> ```<br>
>>><br>
>>> 2. The method is a factory method; such calls should mirror<br>
>>> initializers, with no preposition. For example,<br>
>>> ```<br>
>>> let x = UIColor(red: r, green: g, blue: b)<br>
>>> let y = monitor.makeColor(red: r, green: g, blue: b)<br>
>>> ```<br>
>><br>
>> If rule B.2 didn't exist<br>
>><br>
>> let y = monitor.makeColor(red: r, green: g, blue: b)<br>
>><br>
>> would still have the first argument labeled by B.1 wouldn't it?<br>
><br>
> Yes, but you could have done this grammatically, as<br>
><br>
> let y = monitor.makeColorHavingRed(r, green: g, blue: b)<br>
><br>
> That's what B2 is designed to prevent.<br>
><br>
>> (Though without this rule, the guidelines wouldn't be clear on whether<br>
>> or not to include prepositions in the argument labels.)<br>
>><br>
>>><br>
>>> 3. It is part of a prepositional phrase<br>
>>><br>
>>> a. The label normally starts with the preposition.<br>
>>> For example,<br>
>>> ```<br>
>>> x.move(from: a, to: b)<br>
>>> x.loadValues(forKeys: ["fox", "box", "lox"])<br>
>>> ```<br>
>>> b. ...unless the preposition would break a very tight association<br>
>>> between parameters:<br>
>>> ```<br>
>>> x.moveTo(x: a, y: b)<br>
>>> ```<br>
>>> [encourage grouping parameters into higher-level concepts,<br>
>>> e.g. Point, in these cases]<br>
>> This seems clear and straightforward to apply. The only place where<br>
>> this isn't totally clear is when there are multiple prepositions (as<br>
>> highlighted in Jacob's response),<br>
><br>
> Multiple prepositions before the first argument?<br>
<br>
</div></div>Yes, before and including the first argument label. For example (from Jacob's response):<br>
<span><br>
comparePositionInDecodeOrderWithPosition(of cursor: AVSampleCursor) -> ComparisonResult<br>
<br>
</span>Jacob suggests spelling it:<br>
<br>
comparePositionInDecodeOrder(withPositionOf cursor: AVSampleCursor) -> ComparisonResult<br>
<br>
I agree that Jacob's spelling is better, but not enough better to justify additional guidelines about prepositions.<br></blockquote><div><br></div><div>To clarify/be precise, the guidelines as written are clear on how to treat this: put the prepositional phrase completed by the first argument in the argument label (unless B.3.b applies). </div><div><br></div><div>Where the ambiguity arises is in deciding whether the first argument completes the prepositional phrase "of" or "withPositionOf" (or "inDecodeOrderWithPositionOf"). </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
<div><div class="h5"><br>
><br>
>> but I think B.3 provides the right level of guidance... much more<br>
>> detail will start being too many guidelines and special cases.<br>
><br>
> Thanks!<br>
> --<br>
> -Dave<br>
</div></div></blockquote></div><br></div></div>